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

Message-ID: <20260120175548.GA2749368@ax162>
Date: Tue, 20 Jan 2026 10:55:48 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Guillaume Tucker <gtucker@...cker.io>
Cc: 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

On Tue, Jan 20, 2026 at 10:46:15AM +0100, Guillaume Tucker wrote:
> Well the tuxmake LLVM image is mentioned in the first example:
> 
>     scripts/container -i tuxmake/korg-clang -- make LLVM=1 defconfig
>     scripts/container -i tuxmake/korg-clang -- make LLVM=1 -j$(nproc)
> 
> So that should just work out of the box.  Or did you mean to add
> something else to the docs?

I was just envisioning a blurb like "Additionally, TuxMake has prebuilt
containers for various architectures: https://hub.docker.com/u/tuxmake"
or something like that at the end of the paragraph before "To build just
``bzImage`` using Clang::" in the documentation.

> But yes, the topic of available container images will be something to
> expand upon once the tool starts getting used.  If things go well
> with this initial version then we can try and move forward with
> hosting first-party images as per the other discussion thread:
> 
>     https://lore.kernel.org/all/cc737636-2a43-4a97-975e-4725733f7ee4@gtucker.io/

Yeah hopefully usage of this tool will spur some movement on that
discussion thread.

Cheers,
Nathan