linux-kernel - Re: [GIT PULL] x86/urgent for v5.13-rc5

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

Date:   Sun, 6 Jun 2021 12:38:32 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Borislav Petkov <bp@...e.de>, Mike Rapoport <rppt@...ux.ibm.com>
Cc:     x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] x86/urgent for v5.13-rc5

On Sun, Jun 6, 2021 at 12:55 AM Borislav Petkov <bp@...e.de> wrote:
>
> - Do away with all the wankery of reserving X amount of memory in
> the first megabyte to prevent BIOS corrupting it and simply and
> unconditionally reserve the whole first megabyte.

This seems a bit draconic.

How does this work at all under Windows? There must be some windows
knowledge about what the BIOS updates that we're not aware of.

I've pulled it, but it does seem like something odd is going on.

And that

    Fixes: a799c2bd29d1 ("x86/setup: Consolidate early memory reservations")

makes me go "Umm.." too. What did a799c2bd29d1 actually break? It
looks like it was meant to be a no-op consolidation - if somebody
bisected to it, I think that is a sign that there's something odd
there.

           Linus