From: Paolo Valente <paolo.valente@linaro.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Holger Hoffstätte" <holger@applied-asynchrony.com>
Subject: Re: [PATCH] Revert "Revert "block, bfq: honor already-setup queue merges""
Date: Tue, 8 Mar 2022 10:59:22 +0100 [thread overview]
Message-ID: <82461016-858C-487B-B3B2-ED0008BB2501@linaro.org> (raw)
In-Reply-To: <20211125181510.15004-1-paolo.valente@linaro.org>
> Il giorno 25 nov 2021, alle ore 19:15, Paolo Valente <paolo.valente@linaro.org> ha scritto:
>
> A crash [1] happened to be triggered in conjunction with commit
> 2d52c58b9c9b ("block, bfq: honor already-setup queue merges"). The
> latter was then reverted by commit ebc69e897e17 ("Revert "block, bfq:
> honor already-setup queue merges""). Yet, the reverted commit was not
> the one introducing the bug. In fact, it actually triggered a UAF
> introduced by a different commit, and now fixed by commit d29bd41428cf
> ("block, bfq: reset last_bfqq_created on group change").
>
> So, there is no point in keeping commit 2d52c58b9c9b ("block, bfq:
> honor already-setup queue merges") out. This commit restores it.
>
Hi,
this patch does not seem to have been applied yet (or at least
commented if there are still problems).
Thanks,
Paolo
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=214503
>
> Reported-by: Holger Hoffstätte <holger@applied-asynchrony.com>
> Signed-off-by: Paolo Valente <paolo.valente@linaro.org>
> ---
> block/bfq-iosched.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
> index fec18118dc30..7cde7a11c42b 100644
> --- a/block/bfq-iosched.c
> +++ b/block/bfq-iosched.c
> @@ -2662,6 +2662,15 @@ bfq_setup_merge(struct bfq_queue *bfqq, struct bfq_queue *new_bfqq)
> * are likely to increase the throughput.
> */
> bfqq->new_bfqq = new_bfqq;
> + /*
> + * The above assignment schedules the following redirections:
> + * each time some I/O for bfqq arrives, the process that
> + * generated that I/O is disassociated from bfqq and
> + * associated with new_bfqq. Here we increases new_bfqq->ref
> + * in advance, adding the number of processes that are
> + * expected to be associated with new_bfqq as they happen to
> + * issue I/O.
> + */
> new_bfqq->ref += process_refs;
> return new_bfqq;
> }
> @@ -2724,6 +2733,10 @@ bfq_setup_cooperator(struct bfq_data *bfqd, struct bfq_queue *bfqq,
> {
> struct bfq_queue *in_service_bfqq, *new_bfqq;
>
> + /* if a merge has already been setup, then proceed with that first */
> + if (bfqq->new_bfqq)
> + return bfqq->new_bfqq;
> +
> /*
> * Check delayed stable merge for rotational or non-queueing
> * devs. For this branch to be executed, bfqq must not be
> @@ -2825,9 +2838,6 @@ bfq_setup_cooperator(struct bfq_data *bfqd, struct bfq_queue *bfqq,
> if (bfq_too_late_for_merging(bfqq))
> return NULL;
>
> - if (bfqq->new_bfqq)
> - return bfqq->new_bfqq;
> -
> if (!io_struct || unlikely(bfqq == &bfqd->oom_bfqq))
> return NULL;
>
> --
> 2.20.1
>
prev parent reply other threads:[~2022-03-08 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 18:15 [PATCH] Revert "Revert "block, bfq: honor already-setup queue merges"" Paolo Valente
2022-03-08 9:59 ` Paolo Valente [this message]
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=82461016-858C-487B-B3B2-ED0008BB2501@linaro.org \
--to=paolo.valente@linaro.org \
--cc=axboe@kernel.dk \
--cc=holger@applied-asynchrony.com \
--cc=linux-block@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).