All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Jinchao <wangjinchao@xfusion.com>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
	<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<nstange@suse.de>, <tangqingmei@xfusion.com>,
	<stone.xulei@xfusion.com>
Subject: Re: Issue: padata: UAF in padata_serial_worker reproduce
Date: Thu, 21 Sep 2023 08:50:17 +0800	[thread overview]
Message-ID: <ZQuTSeIskyDjkiMg@fedora> (raw)
In-Reply-To: <lq67pqfz4ucmrpbwmor7h23x2iafsnyh4yuz3mfrfaxrsqbyxz@wqp5rih7grwp>

On Mon, Sep 18, 2023 at 09:21:59AM -0400, Daniel Jordan wrote:
> Hi,
> 
> On Mon, Sep 18, 2023 at 02:27:34PM +0800, Wang Jinchao wrote:
> > Hello, I have reproduced the issue mentioned by Nicolai Stange on an arm64 server.
> > After applying Nicolai Stange's patch, the issue did not reoccur even after running for two days.
> > The test tools used were ltp20220121 and stress-ng-0.15.06.tar.gz.
> > 
> > refurl: https://lore.kernel.org/all/20221028160401.cccypv4euxikusiq@parnassus.localdomain/T/#u
> 
> Yeah, this series seems close to being finished, just hasn't made it
> over the finish line quite yet.  I wonder if Nicolai has plans to
> ressurect or whether someone else should take it over.

Hello, I'd like to inquire about something:

Since users of padata_free_shell need to ensure that all tasks in padata_shell have completed, 
how can they confirm this when they are uncertain? Would it be better if Padata provided a mechanism, 
such as padata_shell_status(), to maintain statistics like the number of tasks?

Thanks

  reply	other threads:[~2023-09-21  1:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  6:27 Issue: padata: UAF in padata_serial_worker reproduce Wang Jinchao
2023-09-18 13:21 ` Daniel Jordan
2023-09-21  0:50   ` Wang Jinchao [this message]
2023-10-04 14:54     ` Daniel Jordan
2023-09-28  8:59   ` Wang Jinchao

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=ZQuTSeIskyDjkiMg@fedora \
    --to=wangjinchao@xfusion.com \
    --cc=daniel.m.jordan@oracle.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nstange@suse.de \
    --cc=steffen.klassert@secunet.com \
    --cc=stone.xulei@xfusion.com \
    --cc=tangqingmei@xfusion.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.