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: <87bk9d301n.fsf@kernel.org>
Date: Mon, 22 Jan 2024 16:39:00 +0200
From: Kalle Valo <kvalo@...nel.org>
To: Johan Hovold <johan@...nel.org>
Cc: Johan Hovold <johan+linaro@...nel.org>,  Jeff Johnson
 <quic_jjohnson@...cinc.com>,  ath11k@...ts.infradead.org,
  linux-wireless@...r.kernel.org,  linux-kernel@...r.kernel.org
Subject: Re: ath11k: checking RCU usage

Johan Hovold <johan@...nel.org> writes:

> On Mon, Jan 22, 2024 at 02:10:17PM +0100, Johan Hovold wrote:
>> On Sat, Jan 13, 2024 at 12:26:53PM +0200, Kalle Valo wrote:
>
>> > I just found out that sparse has __must_hold():
>> > 
>> > https://lore.kernel.org/linux-wireless/87sf31hhfp.fsf@kernel.org/
>> > 
>> > That looks promising, should we start using that in ath11k and ath12k to
>> > check our RCU usage?
>> 
>> I see that Johannes already commented on this in the thread above.
>> 
>> I'm pretty sure smatch can't be used for this.
>
> I meant "sparse"...

Yeah, that was a disappointment. I should have tested it first :)

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ