lkdtm: Remove references to CONFIG_REFCOUNT_FULL
authorWill Deacon <will@kernel.org>
Thu, 21 Nov 2019 11:59:02 +0000 (11:59 +0000)
committerIngo Molnar <mingo@kernel.org>
Mon, 25 Nov 2019 08:15:46 +0000 (09:15 +0100)
CONFIG_REFCOUNT_FULL no longer exists, so remove all references to it.

Signed-off-by: Will Deacon <will@kernel.org>
Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Acked-by: Kees Cook <keescook@chromium.org>
Tested-by: Hanjun Guo <guohanjun@huawei.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Elena Reshetova <elena.reshetova@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/20191121115902.2551-11-will@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
drivers/misc/lkdtm/refcount.c

index abf3b7c1f686c13d3c7c0f782cc175fa719001cc..de7c5ab528d9efa6ef1d633ef37de2fe61b44304 100644 (file)
@@ -119,7 +119,7 @@ void lkdtm_REFCOUNT_DEC_ZERO(void)
 static void check_negative(refcount_t *ref, int start)
 {
        /*
-        * CONFIG_REFCOUNT_FULL refuses to move a refcount at all on an
+        * refcount_t refuses to move a refcount at all on an
         * over-sub, so we have to track our starting position instead of
         * looking only at zero-pinning.
         */
@@ -202,7 +202,6 @@ static void check_from_zero(refcount_t *ref)
 
 /*
  * A refcount_inc() from zero should pin to zero or saturate and may WARN.
- * Only CONFIG_REFCOUNT_FULL provides this protection currently.
  */
 void lkdtm_REFCOUNT_INC_ZERO(void)
 {