netdev - Re: [PATCH net-next] stddef: don't include compiler

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: <20250826064755.6462354d@kernel.org>
Date: Tue, 26 Aug 2025 06:47:55 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Kees Cook <kees@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
 dhowells@...hat.com, gustavoars@...nel.org, aleksander.lobakin@...el.com,
 tstruk@...aio.com
Subject: Re: [PATCH net-next] stddef: don't include compiler_types.h in the
 uAPI header

On Mon, 25 Aug 2025 19:54:44 -0700 Kees Cook wrote:
> > Not sure this is the most fortunate approach, personally I'd rather wrap
> > our empty user-space-facing defines under ifndef __KERNEL__. I think
> > it'd be better from "include what you need" perspective. Perhaps stddef
> > pulling in compiler annotations is expected, dunno...  
> 
> I'm trying to leave the door open for userspace to start using these, if
> they defined them too.

Makes sense.