Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 28 Oct 2022 12:59:34 +0100
From:   Catalin Marinas <catalin.marinas@arm.com>
To:     "zhaoyang.huang" <zhaoyang.huang@unisoc.com>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        Matthew Wilcox <willy@infradead.org>,
        Zhaoyang Huang <huangzhaoyang@gmail.com>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, ke.wang@unisoc.com,
        steve.kang@unisoc.com
Subject: Re: [PATCHv2] mm: introduce NR_BAD_PAGES and track them via kmemleak
Message-ID: <Y1vEJo0d9GkzJY1Q@arm.com>
References: <1663730246-11968-1-git-send-email-zhaoyang.huang@unisoc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1663730246-11968-1-git-send-email-zhaoyang.huang@unisoc.com>
Precedence: bulk

On Wed, Sep 21, 2022 at 11:17:26AM +0800, zhaoyang.huang wrote:
> From: Zhaoyang Huang <zhaoyang.huang@unisoc.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@unisoc.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