From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH for-current 0/2] sqo files/mm fixes
Date: Thu, 14 Jan 2021 21:12:05 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/01/2021 04:00, Pavel Begunkov wrote:
> Neither of issues is confirmed, but should be a good hardening in any
> case. Inefficiencies will be removed for-next.
A reminder just in case it was lost
>
> Pavel Begunkov (2):
> io_uring: drop mm and files after task_work_run
> io_uring: don't take files/mm for a dead task
>
> fs/io_uring.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-01-14 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 4:00 [PATCH for-current 0/2] sqo files/mm fixes Pavel Begunkov
2021-01-11 4:00 ` [PATCH 1/2] io_uring: drop mm and files after task_work_run Pavel Begunkov
2021-01-11 4:00 ` [PATCH 2/2] io_uring: don't take files/mm for a dead task Pavel Begunkov
2021-01-14 21:12 ` Pavel Begunkov [this message]
2021-01-14 23:28 ` [PATCH for-current 0/2] sqo files/mm fixes Jens Axboe
2021-01-15 12:33 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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