linux-kernel - Re: [PATCH v3 0/2] scripts: introduce containerized builds

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: <4848da1a-91bf-4c2d-a6df-63963ee9f0a3@gtucker.io>
Date: Sat, 31 Jan 2026 14:36:17 +0100
From: Guillaume Tucker <gtucker@...cker.io>
To: Nicolas Schier <nsc@...nel.org>
Cc: Nathan Chancellor <nathan@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
 David Gow <davidgow@...gle.com>, Onur Özkan
 <work@...rozkan.dev>, Arnd Bergmann <arnd@...db.de>,
 linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
 linux-kbuild@...r.kernel.org, automated-testing@...ts.yoctoproject.org,
 workflows@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH v3 0/2] scripts: introduce containerized builds

Hi Nicolas,

On 27/01/2026 9:13 pm, Nicolas Schier wrote:
> On Thu, Jan 22, 2026 at 03:12:36PM +0100, Guillaume Tucker wrote:
>> Hi Nicolas,
>>
>> On 20/01/2026 14:54, Nicolas Schier wrote:
>>> Out-of-source builds do not work on my system with podman.  If this is
>>> expected, I think it would be great to mention that somewhere in the
>>> documentation.
>>
>> The v4 now mentions this and also includes a trick using bind-mount:
>>
>>    mkdir -p $HOME/tmp/my-kernel-build
>>    mkdir -p build
>>    sudo mount --bind $HOME/tmp/my-kernel-build build
>>    scripts/container -i kernel.org/gcc -- make mrproper
>>    scripts/container -i kernel.org/gcc -- make O=build defconfig
>>    scripts/container -i kernel.org/gcc -- make O=build -j$(nproc)
>>
>> Would this work for your use-case?  Directory names are entirely
>> arbitrary.  It's not ideal but might be good enough as a workaround
>> until this gets properly supported by the tool in a future version.
> 
> sorry for the long delay.  Yes, thanks for the follow-up!

Great!  Thank you for confirming.  It's now in linux-next.

Cheers,
Guillaume