linux-kernel - compiler_types.h in UAPI?

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

Message-ID: <ZjUzt3Rysyk-oGdQ@smile.fi.intel.com>
Date: Fri, 3 May 2024 21:57:59 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: David Howells <dhowells@...hat.com>, Arnd Bergmann <arnd@...db.de>
Cc: linux-kernel@...r.kernel.org
Subject: compiler_types.h in UAPI?

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?

-- 
With Best Regards,
Andy Shevchenko