[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aDFsWA43h8ToQUhZ@gondor.apana.org.au>
Date: Sat, 24 May 2025 14:51:04 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Mark Brown <broonie@...nel.org>
Cc: Dominik Grzegorzek <dominik.grzegorzek@...cle.com>,
"aishwarya.tcv@....com" <aishwarya.tcv@....com>,
"chenridong@...wei.com" <chenridong@...wei.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"steffen.klassert@...unet.com" <steffen.klassert@...unet.com>
Subject: Re: [PATCH] padata: do not leak refcount in reorder_work
On Thu, May 22, 2025 at 03:02:14PM +0100, Mark Brown wrote:
>
> The hugepages code does make use of padata and it's a hugepages test so
> there's some potential connection there, definitely not an obvious one
> though.
I just had a look at this and the hugepage use of padata has
nothing to do with the patch in question at all. In fact, the
two users of padata pretty much live in separate universes. The
only connection between them is the shared set of work structs.
So I think is a false-positive bisection result.
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists