From: Jens Axboe <axboe@kernel.dk>
To: jack@suse.cz, paolo.valente@linaro.org
Cc: yukuai3@huawei.com, stable@vger.kernel.org,
linux-block@vger.kernel.org, lists@colorremedies.com
Subject: Re: [PATCH] bfq: Fix warning in bfqq_request_over_limit()
Date: Fri, 29 Apr 2022 06:45:50 -0600 [thread overview]
Message-ID: <165123635009.46786.3093085989076098329.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220407140738.9723-1-jack@suse.cz>
On Thu, 7 Apr 2022 16:07:38 +0200, Jan Kara wrote:
> People are occasionally reporting a warning bfqq_request_over_limit()
> triggering reporting that BFQ's idea of cgroup hierarchy (and its depth)
> does not match what generic blkcg code thinks. This can actually happen
> when bfqq gets moved between BFQ groups while bfqq_request_over_limit()
> is running. Make sure the code is safe against BFQ queue being moved to
> a different BFQ group.
>
> [...]
Applied, thanks!
[1/1] bfq: Fix warning in bfqq_request_over_limit()
commit: 09df6a75fffa68169c5ef9bef990cd7ba94f3eef
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-04-29 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 14:07 [PATCH] bfq: Fix warning in bfqq_request_over_limit() Jan Kara
2022-04-29 12:01 ` Jan Kara
2022-04-29 12:45 ` Jens Axboe [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=165123635009.46786.3093085989076098329.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=paolo.valente@linaro.org \
--cc=stable@vger.kernel.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).