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

Date: Fri, 03 May 2024 21:34:13 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Andy Shevchenko" <andriy.shevchenko@...ux.intel.com>,
 "David Howells" <dhowells@...hat.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: compiler_types.h in UAPI?

On Fri, May 3, 2024, at 20:57, Andy Shevchenko wrote:
> Hi!
>
> Today I have stumbled over use of __force and other compiler_types.h related
> things in UAPI headers. Can anybody explain to me how do they suppose to work
> outside of the kernel? Or did I miss something obvious? Or it was a mistake
> during UAPI split to move swab.h and byteorder/ (most of the users of those)
> to UAPI in the first place?

These get stripped out by scripts/headers_install.sh during
the 'make headers_install' stage:

sed -E -e '
        s/([[:space:](])(__user|__force|__iomem)[[:space:]]/\1/g
        s/__attribute_const__([[:space:]]|$)/\1/g
        s@...nclude <linux/compiler(|_types).h>@@
        s/(^|[^a-zA-Z0-9])__packed([^a-zA-Z0-9_]|$)/\1__attribute__((packed))\2/g
        s/(^|[[:space:](])(inline|asm|volatile)([[:space:](]|$)/\1__\2__\3/g
        s@#(ifndef|define|endif[[:space:]]*/[*])[[:space:]]*_UAPI@#\1 @
' $INFILE > $TMPFILE || exit 1


      Arnd