[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230323151850.e2785b1cff37fba078f26f2b@linux-foundation.org>
Date: Thu, 23 Mar 2023 15:18:50 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Muchun Song <songmuchun@...edance.com>
Cc: glider@...gle.com, elver@...gle.com, dvyukov@...gle.com,
jannh@...gle.com, sjpark@...zon.de, muchun.song@...ux.dev,
kasan-dev@...glegroups.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: kfence: fix handling discontiguous page
On Thu, 23 Mar 2023 10:50:03 +0800 Muchun Song <songmuchun@...edance.com> wrote:
> The struct pages could be discontiguous when the kfence pool is allocated
> via alloc_contig_pages() with CONFIG_SPARSEMEM and !CONFIG_SPARSEMEM_VMEMMAP.
> So, the iteration should use nth_page().
What are the user-visible runtime effects of this flaw?
Thanks.
Powered by blists - more mailing lists