linux-kernel - Re: [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h

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: <5ca9d57f-b711-4929-89ca-79e6966bf3be@sirena.org.uk>
Date: Wed, 21 May 2025 14:58:16 +0100
From: Mark Brown <broonie@...nel.org>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Willy Tarreau <w@....eu>, Shuah Khan <shuah@...nel.org>,
	linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h

On Wed, May 21, 2025 at 03:45:42PM +0200, Thomas Weißschuh wrote:
> On 2025-05-21 14:22:30+0100, Mark Brown wrote:

> > Ah, you expect what's currently there to work - good.  I noticed that
> > the vDSO tests had a -I for the nolibc directory which made me think it
> > was expected that it be there, it's the only user on most arches.

> The -I is useful to compile applications without guarding the system
> includes with #ifndef NOLIBC.

These tests are all nolibc specific and so don't reference the system
headers, the whole point is to not use a real libc.

> What do I have to do to cross-compile these selftests?
> I get various compiler errors.

Any specific errors?  It's just a standard selftest build, eg:

   make -C tools/testing/selftests LLVM=1 ARCH=arm64 TARGETS=arm64

Unless you've got very current userspace headers you'll probably need
a headers_install too (that's generally needed for the selftests).

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)