linux-kernel - Re: Linux 6.1-rc3

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: <CAHk-=whNVbdynjJTe8vdpNZyXZ9Aqr9KppXdD4ZioCETtLeziw@mail.gmail.com>
Date:   Tue, 1 Nov 2022 10:37:04 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Guenter Roeck <linux@...ck-us.net>, Arnd Bergmann <arnd@...db.de>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Masahiro Yamada <masahiroy@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Miguel Ojeda <ojeda@...nel.org>
Subject: Re: Linux 6.1-rc3

On Tue, Nov 1, 2022 at 10:29 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> The random "Inconsistent kallsyms data" issue is something that we've
> had for over a decade.

Actually, it's more like two decades at least.

I had to go back to the BK archives just to see, but that
"Inconsistent kallsyms data" goes back to at least 2004, and that's
just when the warning (and that KALLSYMS_EXTRA_PASS workaround) was
introduced.

The problem itself predates it. The bitkeeper commit from June 2004 by
Keith Owens optimistically states

    Add CONFIG_KALLSYMS_EXTRA_PASS as a temporary workaround for unstable maps,
    so users can proceed while waiting for kallsyms to be fixed.

and here we are, almost two decades later, and that "temporary"
KALLSYMS_EXTRA_PASS thing still exists.

But yeah, it has always been this low-grade annoying randomness with
symbols that move around when re-linking.

             Linus