linux-kernel - Re: [PATCH] mm/kmemleak: Fix percpu memory leak detection failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAFULd4Y7UshG1hk=H0nQKo=iPXVQYta-uWFQJvV1NjRudSavXw@mail.gmail.com>
Date: Fri, 27 Dec 2024 11:42:49 +0100
From: Uros Bizjak <ubizjak@...il.com>
To: Guo Weikang <guoweikang.kernel@...il.com>
Cc: Catalin Marinas <catalin.marinas@....com>, Andrew Morton <akpm@...ux-foundation.org>, 
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/kmemleak: Fix percpu memory leak detection failure

On Fri, Dec 27, 2024 at 11:37 AM Uros Bizjak <ubizjak@...il.com> wrote:
>
> On Fri, Dec 27, 2024 at 10:23 AM Guo Weikang
> <guoweikang.kernel@...il.com> wrote:
> >
> > kmemleak_alloc_percpu gives an incorrect min_count parameter, causing
> > percpu memory to be considered a gray object.
> >
> > Fixes: 8c8685928910 ("mm/kmemleak: use IS_ERR_PCPU() for pointer in the percpu address space")
> >
> > Signed-off-by: Guo Weikang <guoweikang.kernel@...il.com>
>
> I don't know how 1 turned to 0, the change was definitely unintended.

Looking at the original patch at [1], it looks like a mismerge to me.

[1] https://lore.kernel.org/all/20240818210235.33481-2-ubizjak@gmail.com/T/#u

Uros.