Re: [PATCH] locking/refcount: Use REFCOUNT_WARN() to simplify code

From: Will Deacon
Date: Mon Apr 04 2022 - 05:31:15 EST


On Wed, Mar 16, 2022 at 08:51:14PM +0800, Zhen Lei wrote:
> To avoid the check "new > val" appears twice, and make the style
> consistent with that in refcount_warn_saturate().
>
> Signed-off-by: Zhen Lei <thunder.leizhen@xxxxxxxxxx>
> ---
> lib/refcount.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/refcount.c b/lib/refcount.c
> index a207a8f22b3ca35..d36aa3fa728f53b 100644
> --- a/lib/refcount.c
> +++ b/lib/refcount.c
> @@ -84,7 +84,7 @@ bool refcount_dec_not_one(refcount_t *r)
>
> new = val - 1;
> if (new > val) {
> - WARN_ONCE(new > val, "refcount_t: underflow; use-after-free.\n");
> + REFCOUNT_WARN("underflow; use-after-free");
> return true;
> }

Acked-by: Will Deacon <will@xxxxxxxxxx>

Will