From: Muchun Song <songmuchun@bytedance.com>
To: axboe@kernel.dk, viro@zeniv.linux.org.uk
Cc: linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Muchun Song <songmuchun@bytedance.com>
Subject: [PATCH 0/3] io_uring: Fix async workqueue is not canceled on some corner case
Date: Tue, 15 Sep 2020 16:15:48 +0800 [thread overview]
Message-ID: <20200915081551.12140-1-songmuchun@bytedance.com> (raw)
We should make sure that async workqueue is canceled on exit, but on
some corner case, we found that the async workqueue is not canceled
on exit in the linux-5.4. So we started an in-depth investigation.
Fortunately, we finally found the problem. The commit:
1c4404efcf2c ("io_uring: make sure async workqueue is canceled on exit")
did not completely solve this problem. This patch series to solve this
problem completely. And there's no upstream variant of this commit, so
this patch series is just fix the linux-5.4.y stable branch.
Muchun Song (2):
io_uring: Fix missing smp_mb() in io_cancel_async_work()
io_uring: Fix remove irrelevant req from the task_list
Yinyin Zhu (1):
io_uring: Fix resource leaking when kill the process
fs/io_uring.c | 45 +++++++++++++++++++++++++++++----------------
1 file changed, 29 insertions(+), 16 deletions(-)
--
2.11.0
next reply other threads:[~2020-09-15 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 8:15 Muchun Song [this message]
2020-09-15 8:15 ` [PATCH 1/3] io_uring: Fix resource leaking when kill the process Muchun Song
2020-09-15 8:15 ` [PATCH 2/3] io_uring: Fix missing smp_mb() in io_cancel_async_work() Muchun Song
2020-09-15 8:15 ` [PATCH 3/3] io_uring: Fix remove irrelevant req from the task_list Muchun Song
2020-09-15 9:44 ` [PATCH 0/3] io_uring: Fix async workqueue is not canceled on some corner case Greg KH
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=20200915081551.12140-1-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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).