All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] block: Make request_queue lockdep splats show up earlier
Date: Tue, 18 Mar 2025 16:10:08 +0800	[thread overview]
Message-ID: <Z9kqYBnvrxBckn-u@fedora> (raw)
In-Reply-To: <fa077596a112c9cae51905cff0987755db2a7934.camel@linux.intel.com>

On Tue, Mar 18, 2025 at 08:56:18AM +0100, Thomas Hellström wrote:
> On Tue, 2025-03-18 at 09:18 +0800, Ming Lei wrote:
> > On Mon, Mar 17, 2025 at 06:11:55PM +0100, Thomas Hellström wrote:

...

> 
> One caveat though. If this is merged, people will probably start seeing
> the lockdep splat as a regression and bisects will point to this commit
> demanding the potential deadlock(s) to be fixed.

Don't worry, just keep linux-block@ updated with the report.

> 
> Is there a line of sight to fix the real deadlock?

The linux-block community has solved many such warnings recently, and your
patch could expose more, and we will try to address new coming reports as
before.


Thanks,
Ming


      reply	other threads:[~2025-03-18  8:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 17:11 [RFC PATCH] block: Make request_queue lockdep splats show up earlier Thomas Hellström
2025-03-17 17:37 ` Bart Van Assche
2025-03-17 18:13   ` Thomas Hellström
2025-03-17 18:28     ` Bart Van Assche
2025-03-17 18:38       ` Thomas Hellström
2025-03-18  1:18 ` Ming Lei
2025-03-18  7:56   ` Thomas Hellström
2025-03-18  8:10     ` Ming Lei [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=Z9kqYBnvrxBckn-u@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.hellstrom@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.