From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ebiederm@xmission.com
Subject: [PATCH 0/2] don't use pid for request cancellation
Date: Mon, 15 Jun 2020 10:33:12 +0300 [thread overview]
Message-ID: <cover.1592206077.git.asml.silence@gmail.com> (raw)
Cancel requests of an extiting task based on ->task address. As
reported by Eric W. Biederman, using pid for this purpose is not
right.
note: rebased on top of "cancel all" patches
Pavel Begunkov (2):
io_uring: lazy get task
io_uring: cancel by ->task not pid
fs/io-wq.h | 1 -
fs/io_uring.c | 46 ++++++++++++++++++++++++++++------------------
2 files changed, 28 insertions(+), 19 deletions(-)
--
2.24.0
next reply other threads:[~2020-06-15 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 7:33 Pavel Begunkov [this message]
2020-06-15 7:33 ` [PATCH 1/2] io_uring: lazy get task Pavel Begunkov
2020-06-15 7:33 ` [PATCH 2/2] io_uring: cancel by ->task not pid Pavel Begunkov
2020-06-15 15:04 ` [PATCH 0/2] don't use pid for request cancellation Jens Axboe
2020-06-15 16:01 ` Pavel Begunkov
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=cover.1592206077.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=ebiederm@xmission.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).