UPSTREAM: kasan: fix conflict with page poisoning
When page poisoning is enabled, it accesses memory that is marked as
poisoned by KASAN, which leas to false-positive KASAN reports.
Suppress the reports by adding KASAN annotations to unpoison_page()
(poison_page() already has them).
Link: https://lkml.kernel.org/r/2dc799014d31ac13fd97bd906bad33e16376fc67.1617118501.git.andreyknvl@google.com
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Marco Elver <elver@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Andrey Konovalov <andreyknvl@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
(cherry picked from commit 06b1f85588)
Bug: 192912968
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: Ica725587c8c72e7b96ac3948799c77a48f27c2e2
This commit is contained in:
committed by
Suren Baghdasaryan
parent
a3da917661
commit
f215850ea0
@@ -77,12 +77,14 @@ static void unpoison_page(struct page *page)
|
||||
void *addr;
|
||||
|
||||
addr = kmap_atomic(page);
|
||||
kasan_disable_current();
|
||||
/*
|
||||
* Page poisoning when enabled poisons each and every page
|
||||
* that is freed to buddy. Thus no extra check is done to
|
||||
* see if a page was poisoned.
|
||||
*/
|
||||
check_poison_mem(addr, PAGE_SIZE);
|
||||
check_poison_mem(kasan_reset_tag(addr), PAGE_SIZE);
|
||||
kasan_enable_current();
|
||||
kunmap_atomic(addr);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user