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

Date:   Fri, 5 Feb 2021 07:54:55 +0100
From:   Greg KH <greg@...ah.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Mike Rapoport <rppt@...ux.ibm.com>,
        Chris Wilson <chris@...is-wilson.co.uk>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>
Subject: Re: Linux 5.11-rc5

On Thu, Feb 04, 2021 at 10:32:56AM -0800, Linus Torvalds wrote:
> On Thu, Feb 4, 2021 at 10:19 AM Mike Rapoport <rppt@...ux.ibm.com> wrote:
> >
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > >
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
> >
> > Unfortunately, I was too optimistic and didn't take into account that this
> > commit changes the way /dev/mem sees the first page of memory.
> >
> > There were reports of slackware users about issues with lilo after upgrade
> > from 5.10.11 to 5.10.12
> 
> Ok, applied to mainline.
> 
> Greg & stable people - this is now commit 5c279c4cf206 ("Revert
> "x86/setup: don't remove E820_TYPE_RAM for pfn 0"") in my tree.
> Although maybe you just want to revert the commit in stable, rather
> than take it from upstream? Same difference.

Taking it from upstream makes it easier to track over time what happend.
I've queued it up now, thanks!

greg k-h