From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: viro@zeniv.linux.org.uk
Subject: [PATCH 0/2] Harden async submit checks
Date: Fri, 23 Jul 2021 11:59:43 -0600 [thread overview]
Message-ID: <20210723175945.354481-1-axboe@kernel.dk> (raw)
Hi,
Patch 1 ensures that we don't resubmit from release, which doesn't
make sense for the reasons outlined in that patch. Patch 2 just adds
a proactive safety check in case we do add a bug that can cause that
to happen, as it might be problematic for those future cases if they
can happen for request types that won't naturally fail.
--
Jens Axboe
next reply other threads:[~2021-07-23 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 17:59 Jens Axboe [this message]
2021-07-23 17:59 ` [PATCH 1/2] io_uring: never attempt iopoll reissue from release path Jens Axboe
2021-07-23 17:59 ` [PATCH 2/2] io_uring: explicitly catch any illegal async queue attempt Jens Axboe
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=20210723175945.354481-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).