[Devel,rh7,05/39] mm/mempool: avoid KASAN marking mempool poison checks as use-after-free

Submitted by Andrey Ryabinin on Sept. 14, 2017, 4:51 p.m.


Message ID 20170914165156.28876-5-aryabinin@virtuozzo.com
State New
Series "Series without cover letter"
Headers show

Commit Message

Andrey Ryabinin Sept. 14, 2017, 4:51 p.m.
From: Matthew Dawson <matthew@mjdsystems.ca>

When removing an element from the mempool, mark it as unpoisoned in KASAN
before verifying its contents for SLUB/SLAB debugging.  Otherwise KASAN
will flag the reads checking the element use-after-free writes as
use-after-free reads.

Signed-off-by: Matthew Dawson <matthew@mjdsystems.ca>
Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

(cherry picked from commit 7640131032db9118a78af715ac77ba2debeeb17c)
Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
 mm/mempool.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch hide | download patch | download mbox

diff --git a/mm/mempool.c b/mm/mempool.c
index d9fa60d6f098..791ec8a148b4 100644
--- a/mm/mempool.c
+++ b/mm/mempool.c
@@ -135,8 +135,8 @@  static void *remove_element(mempool_t *pool)
 	void *element = pool->elements[--pool->curr_nr];
 	BUG_ON(pool->curr_nr < 0);
-	check_element(pool, element);
 	kasan_unpoison_element(pool, element);
+	check_element(pool, element);
 	return element;