On Mon, Oct 07, 2019 at 04:47:03PM +0100, Will Deacon wrote: > CONFIG_REFCOUNT_FULL no longer exists, so remove all references to it.
Same thing: I think this can be collapsed into patch 8. Acked-by: Kees Cook <[email protected]> -Kees > > Cc: Ingo Molnar <[email protected]> > Cc: Elena Reshetova <[email protected]> > Cc: Peter Zijlstra <[email protected]> > Cc: Ard Biesheuvel <[email protected]> > Cc: Kees Cook <[email protected]> > Signed-off-by: Will Deacon <[email protected]> > --- > drivers/misc/lkdtm/refcount.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/drivers/misc/lkdtm/refcount.c b/drivers/misc/lkdtm/refcount.c > index abf3b7c1f686..de7c5ab528d9 100644 > --- a/drivers/misc/lkdtm/refcount.c > +++ b/drivers/misc/lkdtm/refcount.c > @@ -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) > { > -- > 2.23.0.581.g78d2f28ef7-goog > -- Kees Cook
