mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: Dominik Grzegorzek <dominik.grzegorzek@oracle.com>,
	"aishwarya.tcv@arm.com" <aishwarya.tcv@arm.com>,
	"chenridong@huawei.com" <chenridong@huawei.com>,
	Daniel Jordan <daniel.m.jordan@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"steffen.klassert@secunet.com" <steffen.klassert@secunet.com>
Subject: Re: [PATCH] padata: do not leak refcount in reorder_work
Date: Sat, 24 May 2025 14:51:04 +0800	[thread overview]
Message-ID: <aDFsWA43h8ToQUhZ@gondor.apana.org.au> (raw)
In-Reply-To: <01bc9f1e-5a49-4387-b0cb-c2f8647e3b6e@sirena.org.uk>

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@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2025-05-24  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-18 17:45 Dominik Grzegorzek
2025-05-19  1:39 ` Chen Ridong
2025-05-19  6:03 ` Herbert Xu
2025-05-20 16:00 ` Daniel Jordan
2025-05-22 13:10 ` Aishwarya
2025-05-22 13:44   ` Dominik Grzegorzek
2025-05-22 14:02     ` Mark Brown
2025-05-24  6:51       ` Herbert Xu [this message]
2025-05-23  3:48   ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aDFsWA43h8ToQUhZ@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=aishwarya.tcv@arm.com \
    --cc=broonie@kernel.org \
    --cc=chenridong@huawei.com \
    --cc=daniel.m.jordan@oracle.com \
    --cc=dominik.grzegorzek@oracle.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®