linux-kernel - [RFC 0/2] refcount: attempt to avoid imbalance warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220630135934.1799248-1-aahringo@redhat.com>
Date:   Thu, 30 Jun 2022 09:59:32 -0400
From:   Alexander Aring <aahringo@...hat.com>
To:     will@...nel.org
Cc:     peterz@...radead.org, boqun.feng@...il.com, mark.rutland@....com,
        thunder.leizhen@...wei.com, jacob.e.keller@...el.com,
        akpm@...ux-foundation.org, linux-sparse@...r.kernel.org,
        cluster-devel@...hat.com, luc.vanoostenryck@...il.com,
        torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
        aahringo@...hat.com
Subject: [RFC 0/2] refcount: attempt to avoid imbalance warnings

Hi,

This patch tries to avoid some sparse warnings related to
refcount_dec_and_lock() and kref_put_lock().

I send this patch series as RFC because it was necessary to do a kref
change after adding __cond_lock() to refcount_dec_and_lock()
functionality.

For me it looks like we do a lot of acrobatics to avoid sparse warnings
here and I really don't know if it's worth the offer. However this is
what I have now...

- Alex

Alexander Aring (2):
  refcount: add __cond_lock() for conditional lock refcount API
  kref: move kref_put_lock() callback to caller

 include/linux/kref.h     | 24 ++++++++----------------
 include/linux/refcount.h | 21 ++++++++++++++++-----
 lib/refcount.c           | 23 ++++++++++++-----------
 3 files changed, 36 insertions(+), 32 deletions(-)

-- 
2.31.1