From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Zizhi Wo <wozizhi@huaweicloud.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"yukuai@fnnas.com" <yukuai@fnnas.com>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"yangerkun@huawei.com" <yangerkun@huawei.com>,
"chengzhihao1@huawei.com" <chengzhihao1@huawei.com>
Subject: Re: [PATCH 0/2] blk-throttle: minor fixes and cleanup
Date: Tue, 17 Mar 2026 11:41:47 +0000 [thread overview]
Message-ID: <abk8PK0cOI_CxieN@shinmob> (raw)
In-Reply-To: <bc5dda8a-7b43-45e2-8888-cf8c37f53483@huaweicloud.com>
On Mar 17, 2026 / 16:13, Zizhi Wo wrote:
>
>
> 在 2026/3/17 15:37, Shinichiro Kawasaki 写道:
> > On Mar 16, 2026 / 16:44, Zizhi Wo wrote:
> > > From: Zizhi Wo <wozizhi@huawei.com>
> > >
> > > This series contains two minor patches for blk-throttle.
> > >
> > > Patch1: simple cleanup
> > > Patch2: fix timer scheduled on tg_flush_bios()
> > >
> > > Zizhi Wo (2):
> > > blk-throttle: remove leftover carryover checks in
> > > tg_within_[bps/iops]_limit
> > > blk-throttle: fix timer scheduled on wrong service_queue in
> > > tg_flush_bios
> >
> > Hello ZiZhi, just FYI. Blktests CI trial run found that this series triggered
> > the failure of the test case throtl/004 with sdebug:
> >
> > throtl/004 (nullb) (delete disk while IO is throttled)
> > throtl/004 (nullb) (delete disk while IO is throttled) [passed]
> > runtime ... 1.667s
> > throtl/004 (sdebug) (delete disk while IO is throttled)
> > throtl/004 (sdebug) (delete disk while IO is throttled) [failed]
> > runtime ... 3.273s
> > --- tests/throtl/004.out 2026-03-16 10:29:46.761897543 +0000
> > +++ /home/fedora/blktests/results/nodev_sdebug/throtl/004.out.bad 2026-03-16 13:31:54.355173644 +0000
> > @@ -1,3 +1,2 @@
> > Running throtl/004
> > -Input/output error
> > Test complete
>
> Hi, I'm very sorry for my oversight. I have already identified the issue
> with the first patch in the patch set and replied to it myself. I will
> review more carefully next time. Please ignore the first patch (although
> the throtl test case did pass locally...)
Thanks for the explanation, no problem for me.
>
> I'd like to ask whether applying only the second patch can pass the
> corresponding tests in your environment?
Sure, I ran throtl/004 on the kernel v7.0-rc4 + the second patch "blk-throttle:
fix timer scheduled on wrong service_queue in tg_flush_bios" only.
Unfortunately, I still see the test case fails for scsi_debug.
next prev parent reply other threads:[~2026-03-17 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 8:44 [PATCH 0/2] blk-throttle: minor fixes and cleanup Zizhi Wo
2026-03-16 8:44 ` [PATCH 1/2] blk-throttle: remove leftover carryover checks in tg_within_[bps/iops]_limit Zizhi Wo
2026-03-16 11:38 ` Zizhi Wo
2026-03-16 8:44 ` [PATCH 2/2] blk-throttle: fix timer scheduled on wrong service_queue in tg_flush_bios Zizhi Wo
2026-03-17 7:37 ` [PATCH 0/2] blk-throttle: minor fixes and cleanup Shinichiro Kawasaki
2026-03-17 8:13 ` Zizhi Wo
2026-03-17 11:41 ` Shinichiro Kawasaki [this message]
2026-03-17 11:58 ` Zizhi Wo
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=abk8PK0cOI_CxieN@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=axboe@kernel.dk \
--cc=chengzhihao1@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=wozizhi@huaweicloud.com \
--cc=yangerkun@huawei.com \
--cc=yukuai@fnnas.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