[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190507170208.GF1747@sasha-vm>
Date: Tue, 7 May 2019 13:02:08 -0400
From: Sasha Levin <sashal@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Alexander Duyck <alexander.duyck@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Mikhail Zaslonko <zaslonko@...ux.ibm.com>,
Gerald Schaefer <gerald.schaefer@...ibm.com>,
Michal Hocko <mhocko@...nel.org>,
Michal Hocko <mhocko@...e.com>,
Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>,
Dave Hansen <dave.hansen@...el.com>,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
Pasha Tatashin <Pavel.Tatashin@...rosoft.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Sasha Levin <alexander.levin@...rosoft.com>,
linux-mm <linux-mm@...ck.org>
Subject: Re: [PATCH AUTOSEL 4.14 62/95] mm, memory_hotplug: initialize struct
pages for the full memory section
On Tue, May 07, 2019 at 09:50:50AM -0700, Linus Torvalds wrote:
>On Tue, May 7, 2019 at 9:31 AM Alexander Duyck
><alexander.duyck@...il.com> wrote:
>>
>> Wasn't this patch reverted in Linus's tree for causing a regression on
>> some platforms? If so I'm not sure we should pull this in as a
>> candidate for stable should we, or am I missing something?
>
>Good catch. It was reverted in commit 4aa9fc2a435a ("Revert "mm,
>memory_hotplug: initialize struct pages for the full memory
>section"").
>
>We ended up with efad4e475c31 ("mm, memory_hotplug:
>is_mem_section_removable do not pass the end of a zone") instead (and
>possibly others - this was just from looking for commit messages that
>mentioned that reverted commit).
I got it wrong then. I'll fix it up and get efad4e475c31 in instead.
Thanks!
--
Thanks,
Sasha
Powered by blists - more mailing lists