[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFyJ0tBPEjiqx43dTZ-o3Ab3DR_HCKUKEOWiafzFSpvn5A@mail.gmail.com>
Date: Thu, 11 Jan 2018 12:17:31 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Pavel Tatashin <pasha.tatashin@...cle.com>,
Andy Lutomirski <luto@...nel.org>,
Hugh Dickins <hughd@...gle.com>, Thomas Voegtle <tv@...96.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>,
Shuah Khan <shuahkh@....samsung.com>, patches@...nelci.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
lkft-triage@...ts.linaro.org, stable <stable@...r.kernel.org>,
Steve Sistare <steven.sistare@...cle.com>
Subject: Re: [PATCH 4.4 00/37] 4.4.110-stable review
On Thu, Jan 11, 2018 at 12:10 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> Nice, but why does this not show up in 4.9 and 4.14 and Linus's tree as
> well on this hardware? Nor on the SLES12 SP3 kernel?
>
> What is different there that 4.4 requires? That worries me more than
> your fix (which looks good to me, fwiw.)
I really think it's simply that since v4.6, we've had commit
67a9108ed431 ("x86/efi: Build our own page table structures"), so no
normal EFI use actually uses the old legacy mapping unless you passed
in "efi=old_map" on the kernel command line.
So the bug is there in all versions, it's just that it's normally only
noticeable in 4.4.
But I might be missing some other difference, so take that with a pinch of salt.
Linus
Powered by blists - more mailing lists