From: Leon Hwang <leon.hwang@linux.dev>
To: Tao Cui <cui.tao@linux.dev>, Jens Axboe <axboe@kernel.dk>
Cc: Tejun Heo <tj@kernel.org>, Josef Bacik <josef@toxicpanda.com>,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, cuitao@kylinos.cn
Subject: Re: [PATCH] blk-iolatency: use spin_lock_irqsave() in iolatency_clear_scaling()
Date: Fri, 17 Jul 2026 13:36:05 +0800 [thread overview]
Message-ID: <418d9e2a-30b8-47d8-b919-6a777e0993f9@linux.dev> (raw)
In-Reply-To: <20260717040653.1999364-1-cui.tao@linux.dev>
On 17/7/26 12:06, Tao Cui wrote:
> From: Tao Cui <cuitao@kylinos.cn>
>
> child_lat.lock is acquired with spin_lock_irqsave() in both
> iolatency_check_latencies() (called from the blkcg_iolatency_done_bio()
> softirq path) and blkiolatency_timer_fn() (timer softirq).
> iolatency_clear_scaling() instead uses a plain spin_lock(), which only
> happens to be safe because both of its callers enter with interrupts
> already disabled:
>
> * iolatency_set_limit() runs under queue_lock via blkg_conf_prep(),
> which returns with the lock held and interrupts disabled;
> * iolatency_pd_offline() runs under queue_lock from blkg_destroy() and
> blkcg_deactivate_policy(), both of which take it with spin_lock_irq().
>
> Take the lock with spin_lock_irqsave()/spin_unlock_irqrestore() so the
> locking is self-contained and consistent with the other two sites, instead
> of relying on an undocumented caller precondition. No functional change.
>
> Signed-off-by: Tao Cui <cuitao@kylinos.cn>
> ---
> block/blk-iolatency.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/block/blk-iolatency.c b/block/blk-iolatency.c
> index cef02b6c5fa9..68b74258cd95 100644
> --- a/block/blk-iolatency.c
> +++ b/block/blk-iolatency.c
> @@ -811,16 +811,17 @@ static void iolatency_clear_scaling(struct blkcg_gq *blkg)
> if (blkg->parent) {
> struct iolatency_grp *iolat = blkg_to_lat(blkg->parent);
> struct child_latency_info *lat_info;
> + unsigned long flags;
> if (!iolat)
> return;
>
> lat_info = &iolat->child_lat;
> - spin_lock(&lat_info->lock);
> + spin_lock_irqsave(&lat_info->lock, flags);
Better to use guard(spinlock_irqsave)(&lat_info->lock).
Thanks,
Leon
> atomic_set(&lat_info->scale_cookie, DEFAULT_SCALE_COOKIE);
> lat_info->last_scale_event = 0;
> lat_info->scale_grp = NULL;
> lat_info->scale_lat = 0;
> - spin_unlock(&lat_info->lock);
> + spin_unlock_irqrestore(&lat_info->lock, flags);
> }
> }
>
next prev parent reply other threads:[~2026-07-17 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 4:06 [PATCH] blk-iolatency: use spin_lock_irqsave() in iolatency_clear_scaling() Tao Cui
2026-07-17 5:36 ` Leon Hwang [this message]
2026-07-17 5:44 ` Tao Cui
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=418d9e2a-30b8-47d8-b919-6a777e0993f9@linux.dev \
--to=leon.hwang@linux.dev \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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