linux-kernel - Re: [PATCH v2 00/11] Start porting UML to nolibc

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: <07b0f2d0-5dfe-49b0-9f86-28f90512dd4e@t-8ch.de>
Date: Sat, 20 Sep 2025 11:30:18 +0200
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Benjamin Berg <benjamin@...solutions.net>
Cc: linux-um@...ts.infradead.org, Willy Tarreau <w@....eu>, 
	linux-kselftest@...r.kernel.org, Arnaldo Carvalho de Melo <acme@...hat.com>, 
	linux-kernel@...r.kernel.org, Benjamin Berg <benjamin.berg@...el.com>
Subject: Re: [PATCH v2 00/11] Start porting UML to nolibc

On 2025-09-19 17:34:09+0200, Benjamin Berg wrote:
> From: Benjamin Berg <benjamin.berg@...el.com>
> 
> This patchset is an attempt to start a nolibc port of UML. The goal is
> to port UML to use nolibc in smaller chunks to make the switch more
> manageable.
> 
> There are three parts to this patchset:
>  * Two patches to use tools/include headers instead of kernel headers
>    for userspace files.
>  * A few nolibc fixes and a new NOLIBC_NO_STARTCODE compile flag for it
>  * Finally nolibc build support for UML and switching two files while
>    adding the appropriate support in nolibc itself.
> 
> v1 of this patchset was
>   https://lore.kernel.org/all/20250915071115.1429196-1-benjamin@sipsolutions.net/
> 
> Changes in v2:
> - add sys/uio.h and sys/ptrace.h to nolibc
> - Use NOLIBC_NO_RUNTIME to disable nolibc startup code
> - Fix out-of-tree build
> - various small improvements and cleanups
> 
> Should the nolibc changes be merged separately or could everything go
> through the same branch?

Both work for me. But only for the next cycle.

> Also, what about tools/include/linux/compiler.h? It seems that was added
> for the tracing code, but it is not clear to me who might ACK that fix.

Some files in tools/ are orphaned. In the past I got some reviews, included
the change in my tree and mentioned it to Linus in my regular pull request.

(...)


Thomas