From: Markus Elfring <Markus.Elfring@web.de>
To: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
syzbot+fc0674cde00b66844470@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com,
"David S. Miller" <davem@davemloft.net>
Subject: Re: crypto: api - Fix use-after-free and race in crypto_spawn_alg
Date: Fri, 10 Apr 2020 11:18:23 +0200 [thread overview]
Message-ID: <44b4aa3d-0d3b-c10a-7d79-5fcc4d76fe98@web.de> (raw)
> Secondly the setting of the DYING flag is racy because we hold
> the read-lock instead of the write-lock. We should instead call
Would an imperative wording be preferred for this change description?
> This patch fixes both problems.
Will another wording alternative become relevant?
Are the provided tags sufficient for such information?
Regards,
Markus
next reply other threads:[~2020-04-10 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 9:18 Markus Elfring [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-06 18:16 WARNING: refcount bug in crypto_destroy_tfm syzbot
2020-04-10 6:09 ` crypto: api - Fix use-after-free and race in crypto_spawn_alg Herbert Xu
2020-04-16 2:17 ` Eric Biggers
2020-04-16 2:25 ` Herbert Xu
2020-04-16 2:30 ` Eric Biggers
2020-04-16 2:42 ` 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=44b4aa3d-0d3b-c10a-7d79-5fcc4d76fe98@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+fc0674cde00b66844470@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).