Revision 83fd66f70a3c1463685ad0e11272fafe9f5fe06d authored by Alexander Potapenko on 20 December 2018, 16:10:15 UTC, committed by Alexander Potapenko on 08 January 2020, 14:07:57 UTC
In order to report uninitialized memory coming from heap allocations
KMSAN has to poison them unless they're created with __GFP_ZERO.

It's handy that we need KMSAN hooks in the places where
init_on_alloc/init_on_free initialization is performed.

Signed-off-by: Alexander Potapenko <glider@google.com>
To: Alexander Potapenko <glider@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Marco Elver <elver@google.com>
Cc: Andrey Konovalov <andreyknvl@google.com>
Cc: linux-mm@kvack.org
---
v3:
 - reverted unrelated whitespace changes

Change-Id: I51103b7981d3aabed747d0c85cbdc85568665871
1 parent 8c8a406
History
File Mode Size
Kconfig -rw-r--r-- 556 bytes
Makefile -rw-r--r-- 201 bytes
af_phonet.c -rw-r--r-- 12.2 KB
datagram.c -rw-r--r-- 4.1 KB
pep-gprs.c -rw-r--r-- 6.0 KB
pep.c -rw-r--r-- 29.7 KB
pn_dev.c -rw-r--r-- 9.5 KB
pn_netlink.c -rw-r--r-- 7.1 KB
socket.c -rw-r--r-- 16.6 KB
sysctl.c -rw-r--r-- 2.2 KB

back to top