linux-kernel - Re: build reproducibility

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 18 Oct 2021 07:59:29 +0200
From:   Willy Tarreau <w@....eu>
To:     Julia Lawall <julia.lawall@...ia.fr>
Cc:     Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org,
        Masahiro Yamada <masahiroy@...nel.org>,
        Michal Marek <michal.lkml@...kovi.net>,
        linux-kbuild@...r.kernel.org
Subject: Re: build reproducibility

On Mon, Oct 18, 2021 at 07:51:13AM +0200, Julia Lawall wrote:
> My impression is that there is a real
> performance problem in 5.11.  The part I don't understand is why once I
> have booted that kernel, all of the kernels I make afterwards have the
> same performance characteristics.
> 
> If I do git clean -dfx, then copy a fixed configuration to .config, and
> then use make olddefconfig, should anything about the currently running
> kernel have an impact on the kernel that is produced?

Normally not at all, especially if you restart from a fixed .config. By
the way, you should compare the resulting .config after "make oldconfig"
for all your kernels, in case you spot a difference there, but there is
no reason for that difference to depend on the currently running kernel.
Or maybe it detects something related to your machine and adjusts the
.config accordingly, and that detection depends on the running kernel
(e.g. CPU affecting default optims etc) ? If that's the case you'll see
it in the final .config.

> I'll try simply rebooting the machine on each git bisect step.  That
> should eliminate one more aspect of local state.

Just to be avoid wasting your time, perform a cold reboot (reset button).
If you just do a hot reboot and the problem persists, there will still
be a tiny part of doubt leaving a "what if" in your mind that will make
you want to run it all again.

Willy