[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210112052508.GF1106298@kernel.org>
Date: Tue, 12 Jan 2021 07:25:08 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Andrea Arcangeli <aarcange@...hat.com>,
Baoquan He <bhe@...hat.com>, Borislav Petkov <bp@...en8.de>,
David Hildenbrand <david@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Mel Gorman <mgorman@...e.de>, Michal Hocko <mhocko@...nel.org>,
Mike Rapoport <rppt@...ux.ibm.com>, Qian Cai <cai@....pw>,
Thomas Gleixner <tglx@...utronix.de>,
Vlastimil Babka <vbabka@...e.cz>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, x86@...nel.org
Subject: Re: [PATCH v3 0/2] mm: fix initialization of struct page for holes
in memory layout
On Mon, Jan 11, 2021 at 04:58:01PM -0800, Andrew Morton wrote:
> On Mon, 11 Jan 2021 21:40:15 +0200 Mike Rapoport <rppt@...nel.org> wrote:
>
> > Commit 73a6e474cb37 ("mm: memmap_init: iterate over
> > memblock regions rather that check each PFN") exposed several issues with
> > the memory map initialization and these patches fix those issues.
> >
> > Initially there were crashes during compaction that Qian Cai reported back
> > in April [1]. It seemed back then that the problem was fixed, but a few
> > weeks ago Andrea Arcangeli hit the same bug [2] and there was an additional
> > discussion at [3].
>
> The earlier version of these fixes had cc:stable. Was the omission
> this time deliberate?
Nope, it was accidental.
Thanks for noticing.
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists