mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: nilay@linux.ibm.com, ming.lei@redhat.com, hch@lst.de,
	 Yu Kuai <yukuai@fnnas.com>
Cc: yi.zhang@redhat.com, shinichiro.kawasaki@wdc.com,
	kbusch@kernel.org,  rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com,  linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	 linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] blk-mq: use NOIO context to prevent deadlock during debugfs creation
Date: Tue, 17 Feb 2026 08:37:42 -0700	[thread overview]
Message-ID: <177134266269.373694.2745476582847973429.b4-ty@kernel.dk> (raw)
In-Reply-To: <20260214054350.2322436-1-yukuai@fnnas.com>


On Sat, 14 Feb 2026 13:43:50 +0800, Yu Kuai wrote:
> Creating debugfs entries can trigger fs reclaim, which can enter back
> into the block layer request_queue. This can cause deadlock if the
> queue is frozen.
> 
> Previously, a WARN_ON_ONCE check was used in debugfs_create_files()
> to detect this condition, but it was racy since the queue can be frozen
> from another context at any time.
> 
> [...]

Applied, thanks!

[1/1] blk-mq: use NOIO context to prevent deadlock during debugfs creation
      (no commit info)

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2026-02-17 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14  5:43 Yu Kuai
2026-02-15 13:34 ` Nilay Shroff
2026-02-16 18:28 ` Mohamed Khalfella
2026-02-17  7:01 ` Shinichiro Kawasaki
2026-02-17 15:37 ` 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=177134266269.373694.2745476582847973429.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=nilay@linux.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yi.zhang@redhat.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

all inboxes | Powered by JetHome®