From: Jan Kara <jack@suse.cz>
To: <linux-block@vger.kernel.org>
Cc: Paolo Valente <paolo.valente@linaro.org>,
Jens Axboe <axboe@kernel.dk>, "yukuai (C)" <yukuai3@huawei.com>,
Jan Kara <jack@suse.cz>
Subject: [PATCH 0/4 v5] bfq: Avoid use-after-free when moving processes between cgroups
Date: Fri, 21 Jan 2022 11:56:41 +0100 [thread overview]
Message-ID: <20220121105503.14069-1-jack@suse.cz> (raw)
Hello,
here is the fifth version of my patches to fix use-after-free issues in BFQ
when processes with merged queues get moved to different cgroups. The patches
have survived some beating in my test VM, but so far I fail to reproduce the
original KASAN reports so testing from people who can reproduce them is most
welcome. Kuai, can you please give these patches a run in your setup? Thanks
a lot for your help with fixing this!
Changes since v4:
* Even more aggressive splitting of merged bfq queues to avoid problems with
long merge chains.
Changes since v3:
* Changed handling of bfq group move to handle the case when target of the
merge has moved.
Changes since v2:
* Improved handling of bfq queue splitting on move between cgroups
* Removed broken change to bfq_put_cooperator()
Changes since v1:
* Added fix for bfq_put_cooperator()
* Added fix to handle move between cgroups in bfq_merge_bio()
Honza
Previous versions:
Link: http://lore.kernel.org/r/20211223171425.3551-1-jack@suse.cz # v1
Link: http://lore.kernel.org/r/20220105143037.20542-1-jack@suse.cz # v2
Link: http://lore.kernel.org/r/20220112113529.6355-1-jack@suse.cz # v3
Link: http://lore.kernel.org/r/20220114164215.28972-1-jack@suse.cz # v4
next reply other threads:[~2022-01-21 10:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 10:56 Jan Kara [this message]
2022-01-21 10:56 ` [PATCH 1/4] bfq: Avoid false marking of bic as stably merged Jan Kara
2022-01-21 10:56 ` [PATCH 2/4] bfq: Avoid merging queues with different parents Jan Kara
2022-01-21 10:56 ` [PATCH 3/4] bfq: Split shared queues on move between cgroups Jan Kara
2022-01-21 10:56 ` [PATCH 4/4] bfq: Update cgroup information before merging bio Jan Kara
[not found] ` <4b44e8db-771f-fc08-85f1-52c326f3db18@huawei.com>
2022-01-21 12:28 ` [PATCH 0/4 v5] bfq: Avoid use-after-free when moving processes between cgroups yukuai (C)
2022-01-24 14:02 ` Jan Kara
[not found] ` <75bfe59d-c570-8c1c-5a3c-576791ea84ec@huawei.com>
[not found] ` <20220202190210.xppvatep47duofbq@quack3.lan>
2022-02-02 21:53 ` Jan Kara
2022-02-08 3:56 ` yukuai (C)
[not found] ` <6ec28c27-1dce-33e3-1cb7-2e08892471bb@huawei.com>
2022-02-09 17:40 ` Jan Kara
2022-03-11 6:39 ` yukuai (C)
2022-03-11 11:28 ` Jan Kara
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=20220121105503.14069-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=yukuai3@huawei.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).