linux-kernel - Re: [PATCHv2 1/2] refcount: introduce __refcount_dec_and

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-prev] [day] [month] [year] [list]

Message-ID: <CAK-6q+hh_A0Ldwsmmy0BdagDotNBV=Xgk35ZZQ3DAzB9OXwLgw@mail.gmail.com>
Date: Thu, 1 Feb 2024 09:59:41 -0500
From: Alexander Aring <aahringo@...hat.com>
To: peterz@...radead.org
Cc: will@...nel.org, gfs2@...ts.linux.dev, boqun.feng@...il.com, 
	mark.rutland@....com, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 1/2] refcount: introduce __refcount_dec_and_lock macro

Hi,

On Mon, Nov 13, 2023 at 3:48 PM Alexander Aring <aahringo@...hat.com> wrote:
>
> This patch adds the __refcount_dec_and_lock macro to generate code for a
> lock specific refcount_dec_and_lock implementation. Existing
> refcount_dec_and_lock implementation are updated to use the new
> __refcount_dec_and_lock macro. In future other lock implementation can
> added to use the refcount_dec_and_lock trick to only hold the lock when
> the refcount is going to be zero. Per subsystem own lock implementation
> can use the macro as well to provide such implementation for their own
> locking type.
>

ping? :)

Any chance to bring this upstream?

- Alex