linux-kernel - Re: [PATCH v2 3/5] selftests/nolibc: drop call to mrproper target

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: <20250201100755.GB5849@1wt.eu>
Date: Sat, 1 Feb 2025 11:07:55 +0100
From: Willy Tarreau <w@....eu>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Shuah Khan <shuah@...nel.org>, linux-kselftest@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/5] selftests/nolibc: drop call to mrproper target

On Thu, Jan 23, 2025 at 08:37:39AM +0100, Thomas Weißschuh wrote:
> "mrproper" unnecessarily cleans a lot of files.
> kbuild is smart enough to handle changed configurations,
> so the cleanup is not necessary and only leads to excessive rebuilds.

Generally for me the mrproper has been needed when switching between archs
or configs that leave generated files that pollute the build of others.
Also a typical case is during certain bisects. It has happened to me many
times to completely fail a bisect due to not cleaning everything. With
that said I agree that cleaning by default is painful and I also hate doing
that.

So maybe better get rid of it indeed, and leave it to the user to decide to
clean or not.

Acked-by: Willy Tarreau <w@....eu>

Willy