linux-kernel - Re: [PATCH] static_assert: move before people start using it

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]

Date:   Sun, 10 Mar 2019 22:19:37 +0100
From:   Rasmus Villemoes <linux@...musvillemoes.dk>
To:     Alexey Dobriyan <adobriyan@...il.com>, akpm@...ux-foundation.org
Cc:     linux-kernel@...r.kernel.org, linux@...musvillemoes.dk
Subject: Re: [PATCH] static_assert: move before people start using it

On 10/03/2019 11.51, Alexey Dobriyan wrote:
> Userspace places static_assert() macro at <assert.h>
> 

So? That seems a rather weak argument. We have lots of interfaces that
also exist in userspace which are not declared in similar-named headers
(e.g. we have no stdio.h, which is where snprintf lives). Not to mention
that memcpy and friends are in <linux/string.h>, not a bare <string.h>.
Your assert.h would be the first and only header to live directly in
include/.

If you can somehow convince Andrew to take it you can add a Meh'ed-by me.

Rasmus