From: Jan Kara <jack@suse.cz>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: jack@suse.cz, tj@kernel.org, josef@toxicpanda.com,
axboe@kernel.dk, paolo.valente@unimore.it,
mauro.andreolini@unimore.it, avanzini.arianna@gmail.com,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yukuai3@huawei.com,
yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH for-6.12 2/4] block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator()
Date: Wed, 4 Sep 2024 14:17:23 +0200 [thread overview]
Message-ID: <20240904121723.elseqvr277hzmnd6@quack3> (raw)
In-Reply-To: <20240902130329.3787024-3-yukuai1@huaweicloud.com>
On Mon 02-09-24 21:03:27, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
>
> Consider the following merge chain:
>
> Process 1 Process 2 Process 3 Process 4
> (BIC1) (BIC2) (BIC3) (BIC4)
> Λ | | |
> \--------------\ \-------------\ \-------------\|
> V V V
> bfqq1--------->bfqq2---------->bfqq3----------->bfqq4
>
> IO from Process 1 will get bfqf2 from BIC1 first, then
> bfq_setup_cooperator() will found bfqq2 already merged to bfqq3 and then
> handle this IO from bfqq3. However, the merge chain can be much deeper
> and bfqq3 can be merged to other bfqq as well.
>
> Fix this problem by iterating to the last bfqq in
> bfq_setup_cooperator().
>
> Fixes: 36eca8948323 ("block, bfq: add Early Queue Merge (EQM)")
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
Good catch. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> block/bfq-iosched.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
> index 83adac3e71db..ffaa0d56328a 100644
> --- a/block/bfq-iosched.c
> +++ b/block/bfq-iosched.c
> @@ -2911,8 +2911,12 @@ bfq_setup_cooperator(struct bfq_data *bfqd, struct bfq_queue *bfqq,
> struct bfq_iocq_bfqq_data *bfqq_data = &bic->bfqq_data[a_idx];
>
> /* if a merge has already been setup, then proceed with that first */
> - if (bfqq->new_bfqq)
> - return bfqq->new_bfqq;
> + new_bfqq = bfqq->new_bfqq;
> + if (new_bfqq) {
> + while (new_bfqq->new_bfqq)
> + new_bfqq = new_bfqq->new_bfqq;
> + return new_bfqq;
> + }
>
> /*
> * Check delayed stable merge for rotational or non-queueing
> --
> 2.39.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-09-04 12:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 13:03 [PATCH for-6.12 0/4] block, bfq: fix corner cases related to bfqq merging Yu Kuai
2024-09-02 13:03 ` [PATCH for-6.12 1/4] block, bfq: fix possible UAF for bfqq->bic with merge chain Yu Kuai
2024-09-04 11:51 ` Jan Kara
2024-09-02 13:03 ` [PATCH for-6.12 2/4] block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator() Yu Kuai
2024-09-04 12:17 ` Jan Kara [this message]
2024-09-02 13:03 ` [PATCH for-6.12 3/4] block, bfq: don't break merge chain in bfq_split_bfqq() Yu Kuai
2024-09-04 12:20 ` Jan Kara
2024-09-02 13:03 ` [PATCH for-6.12 4/4] block, bfq: use bfq_reassign_last_bfqq() in bfq_bfqq_move() Yu Kuai
2024-09-04 12:22 ` Jan Kara
2024-09-03 15:51 ` [PATCH for-6.12 0/4] block, bfq: fix corner cases related to bfqq merging Jens Axboe
2024-09-04 1:32 ` Yu Kuai
2024-09-04 2:28 ` Bart Van Assche
2024-09-04 2:45 ` Yu Kuai
2024-09-04 13:55 ` Jens Axboe
2024-09-04 17:17 ` Bart Van Assche
2024-09-05 1:48 ` Yu Kuai
2024-09-04 4:38 ` Ming Lei
2024-09-04 12:29 ` Jan Kara
2024-09-04 13:49 ` Jens Axboe
2024-09-04 13:53 ` Jens Axboe
2024-09-03 15:56 ` 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=20240904121723.elseqvr277hzmnd6@quack3 \
--to=jack@suse.cz \
--cc=avanzini.arianna@gmail.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mauro.andreolini@unimore.it \
--cc=paolo.valente@unimore.it \
--cc=tj@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--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