linux-kernel - Re: Linux 5.11-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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAHk-=wh23BXwBwBgPmt9h2EJztnzKKf=qr5r=B0Hr6BGgZ-QDA@mail.gmail.com>
Date:   Mon, 25 Jan 2021 12:49:39 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Chris Wilson <chris@...is-wilson.co.uk>
Cc:     Mike Rapoport <rppt@...ux.ibm.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.11-rc5

On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <chris@...is-wilson.co.uk> wrote:
>
> Quoting Linus Torvalds (2021-01-25 01:06:40)
> > Mike Rapoport (3):
> ...
> >       mm: fix initialization of struct page for holes in memory layout
>
> We have half a dozen or so different machines in CI that are silently
> failing to boot, that we believe is bisected to this patch.

That commit reverts cleanly - so if you can verify that reverting it
fixes your CI machines, I think that that's the right thing to do for
now, unless Mike can figure out some obvious "Duh!" moment from your
working dmesg.

Mike: should we perhaps revert the first patch too (commit
bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?

                Linus