linux-kernel - Re: [PATCH v3 04/30] ntsync: Introduce NTSYNC_IOC_WAIT

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: <2024041254-that-laurel-30f9@gregkh>
Date: Fri, 12 Apr 2024 08:16:08 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Elizabeth Figura <zfigura@...eweavers.com>
Cc: Arnd Bergmann <arnd@...db.de>, Jonathan Corbet <corbet@....net>,
	Shuah Khan <shuah@...nel.org>, linux-kernel@...r.kernel.org,
	linux-api@...r.kernel.org, wine-devel@...ehq.org,
	André Almeida <andrealmeid@...lia.com>,
	Wolfram Sang <wsa@...nel.org>,
	Arkadiusz Hiler <ahiler@...eweavers.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Andy Lutomirski <luto@...nel.org>, linux-doc@...r.kernel.org,
	linux-kselftest@...r.kernel.org,
	Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v3 04/30] ntsync: Introduce NTSYNC_IOC_WAIT_ANY.

On Thu, Apr 11, 2024 at 07:33:07PM -0500, Elizabeth Figura wrote:
> > Rolling your own lock is tricky, and needs review from the locking
> > maintainers.  And probably some more documentation as to what is
> > happening and why our normal types of locks can't be used here?
> 
> Definitely. (Unfortunately this hasn't gotten attention from any locking
> maintainer yet since your last call for review; not sure if there's
> anything I can do there.)

You only seem to have cc:ed one of the "LOCKING PRIMITIVES" maintainers
on this patchset, not all of them, which might be the reason why it has
been ignored :(

Perhaps change that for the next version of this patchset?

thanks,

greg k-h