[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y1vEJo0d9GkzJY1Q@arm.com>
Date: Fri, 28 Oct 2022 12:59:34 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: "zhaoyang.huang" <zhaoyang.huang@...soc.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
Zhaoyang Huang <huangzhaoyang@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, ke.wang@...soc.com,
steve.kang@...soc.com
Subject: Re: [PATCHv2] mm: introduce NR_BAD_PAGES and track them via kmemleak
On Wed, Sep 21, 2022 at 11:17:26AM +0800, zhaoyang.huang wrote:
> From: Zhaoyang Huang <zhaoyang.huang@...soc.com>
>
> Bad pages could be introduced by extra reference among high order pages or compound
> tail pages which cause the pages failed go back to allocator and leaved as orphan
> pages. Booking them down and tracking them via kmemleak.
>
> Signed-off-by: Zhaoyang Huang <zhaoyang.huang@...soc.com>
As I commented previously, I don't understand what bad pages have to do
with kmemleak. Well, you could argue they are memory leaks but kmemleaks
are about logical (software) errors rather than hardware issues.
--
Catalin
Powered by blists - more mailing lists