netdev - Re: [PATCH 0/5] pull request (net-next): ipsec-next 2024-05-03

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

Message-ID: <Zjntq3jSFL2Uud9i@gauss3.secunet.de>
Date: Tue, 7 May 2024 11:00:27 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Simon Horman <horms@...nel.org>
CC: David Miller <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
	Herbert Xu <herbert@...dor.apana.org.au>, <netdev@...r.kernel.org>
Subject: Re: [PATCH 0/5] pull request (net-next): ipsec-next 2024-05-03

On Sat, May 04, 2024 at 03:36:57PM +0100, Simon Horman wrote:
> 
> Hi Steffen, all,
> 
> This comment is not strictly related to this pull request
> and certainly not intended to impede progress of it towards upstream.
> 
> However, while looking over it I noticed that Sparse flags a rather
> large number of warnings in xfrm code, mostly relating to __rcu annotations.
> I'm wondering if, at some point, these could be addressed somehow.

Yes, maybe just start to not introduce new ones and then fix
existing ones over time. I'll have a look on how I can integrate
Sparse checks in my workflow.