[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230913141204.b32ad42ac917c0e393d82a24@linux-foundation.org>
Date: Wed, 13 Sep 2023 14:12:04 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Zi Yan <ziy@...dia.com>
Cc: Zi Yan <zi.yan@...t.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
David Hildenbrand <david@...hat.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Muchun Song <muchun.song@...ux.dev>,
"Mike Rapoport (IBM)" <rppt@...nel.org>
Subject: Re: [PATCH v3 0/5] Use nth_page() in place of direct struct page
manipulation
On Wed, 13 Sep 2023 16:12:43 -0400 Zi Yan <zi.yan@...t.com> wrote:
> On SPARSEMEM without VMEMMAP, struct page is not guaranteed to be
> contiguous, since each memory section's memmap might be allocated
> independently. hugetlb pages can go beyond a memory section size, thus
> direct struct page manipulation on hugetlb pages/subpages might give
> wrong struct page. Kernel provides nth_page() to do the manipulation
> properly. Use that whenever code can see hugetlb pages.
for (each patch) {
Can we please explain why -stable backporting is recommended?
Such an explanation will, as always, include a description of the
user-visible effects of the bug.
Some of the Fixes: targets are very old: 5 years. Has something
changed to bring these flaws to light? Or is it from code inspection?
}
Thanks.
Powered by blists - more mailing lists