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, 28 Sep 2023 16:59:37 +0800 [thread overview]
Message-ID: <ZRVAeZuUxuWjw1D1@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, after a thorough study of padata, I'd like to attempt a refactoring of
padata that doesn't rely on CPUs. The initial results on my personal computer
seem promising. Please review and provide some feedback if possible.
Link: https://lore.kernel.org/all/ZRU%2FEjubEH%2F5QLlG@fedora/
Thanks.
prev parent reply other threads:[~2023-09-28 8:59 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
2023-10-04 14:54 ` Daniel Jordan
2023-09-28 8:59 ` Wang Jinchao [this message]
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=ZRVAeZuUxuWjw1D1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox