Linux cgroups development
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Hao Zhang <hao_zhang_kdev@163.com>
Cc: linux-block@vger.kernel.org, josef@toxicpanda.com,
	axboe@kernel.dk, yukuai@fygo.io, ming.lei@redhat.com,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	dm-devel@lists.linux.dev
Subject: Re: [PATCH] blk-cgroup: save IRQ state in blkg_tryget_closest()
Date: Fri, 11 Sep 2026 06:08:28 -1000	[thread overview]
Message-ID: <aqQnfAjViY7sO1JZ@slm.duckdns.org> (raw)
In-Reply-To: <aqQmqb1k57PXj8Ef@192.168.1.215>

On Sat, Sep 12, 2026 at 12:04:57AM +0800, Hao Zhang wrote:
> From: Hao Zhang <zhanghao1@kylinos.cn>
> 
> bio_set_dev() associates the bio with a blkg through bio_associate_blkg().
> If the blkg lookup misses, blkg_tryget_closest() takes q->queue_lock with
> spin_lock_irq() and releases it with spin_unlock_irq(), which
> unconditionally enables local interrupts.
> 
> Callers may call bio_set_dev() with interrupts already disabled, e.g.
> dm-thin's pool_map() does so while holding pool->lock taken with
> spin_lock_irq().  The nested spin_unlock_irq() then enables interrupts
> while pool->lock is still held, so an I/O completion softirq can run on
> the same CPU, re-acquire pool->lock (thin_endio(), or overwrite_endio()
> -> complete_mapping_preparation()) and deadlock.  lockdep reports this
> as inconsistent SOFTIRQ-ON-W to IN-SOFTIRQ-W usage.
> 
> Commit 3a762de55b4e ("block: save irq state in blkg_lookup_create()")
> fixed the same problem while the lock lived in blkg_lookup_create(), but
> commit 9327a865e395 ("blk-cgroup: don't nest queue_lock under rcu in
> blkg_lookup_create()") moved the locking into blkg_tryget_closest() and
> reverted it to spin_lock_irq().
> 
> Save and restore the caller's IRQ state instead.
> 
> Fixes: 9327a865e395 ("blk-cgroup: don't nest queue_lock under rcu in blkg_lookup_create()")
> Cc: Ming Lei <ming.lei@redhat.com>
> Signed-off-by: Hao Zhang <zhanghao1@kylinos.cn>

Acked-by: Tejun Heo <tj@kernel.org>

Thanks.

-- 
tejun

  reply	other threads:[~2026-09-11 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 16:04 [PATCH] blk-cgroup: save IRQ state in blkg_tryget_closest() Hao Zhang
2026-09-11 16:08 ` Tejun Heo [this message]
2026-09-11 18:32 ` 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=aqQnfAjViY7sO1JZ@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=dm-devel@lists.linux.dev \
    --cc=hao_zhang_kdev@163.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=yukuai@fygo.io \
    /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