[PATCH 2/4] kmemcheck: add __GFP_NOTRACK_FALSE_POSITIVE flag

[Vegard Nossum <vegard.nossum@gmail.com>]

In contrast to __GFP_NOTRACK, this flag indicates that the allocation
should not be tracked _because_ it would produce a false positive.
Their values are identical, but need not be so in the future (for
example, we could now enable/disable false positives with a config
option).

Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
---
 include/linux/gfp.h |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/include/linux/gfp.h b/include/linux/gfp.h
index 2700097..3885e7f 100644
--- a/include/linux/gfp.h
+++ b/include/linux/gfp.h
@@ -58,6 +58,12 @@ struct vm_area_struct;
 #define __GFP_NOTRACK	((__force gfp_t)0)
 #endif
 
+/*
+ * This may seem redundant, but it's a way of annotating false positives vs.
+ * allocations that simply cannot be supported (e.g. page tables).
+ */
+#define __GFP_NOTRACK_FALSE_POSITIVE (__GFP_NOTRACK)
+
 #define __GFP_BITS_SHIFT 22	/* Room for 22 __GFP_FOO bits */
 #define __GFP_BITS_MASK ((__force gfp_t)((1 << __GFP_BITS_SHIFT) - 1))
 
-- 
1.6.0.6