Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-pci: silence a lockdep complaint
Date: Wed, 22 May 2024 21:00:34 +0300	[thread overview]
Message-ID: <a0657f0a-44af-4765-abe3-acc8a1017b40@grimberg.me> (raw)
In-Reply-To: <20240522162845.GA16783@lst.de>



On 22/05/2024 19:28, Christoph Hellwig wrote:
> On Wed, May 22, 2024 at 10:12:19AM -0600, Keith Busch wrote:
>>> Tested-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
>> This is not desireable, but I give up trying to appease lockdep for this
>> one.
> lockdep_off is a cure that's worth than the desease.

This is not ideal for sure.

>   If we can't
> explain the "can't happen" using lockdep classes I don't see how
> we could actually be sure that it can't happen.

I don't understand lockdep well enough to do that. This warning
exists for 6 months now. The conclusion that Keith came to (and I agreed)
is that it can't happen, because nvme_timeout handler will not disable the
device while the ctrl reset_work is running, the ctrl state machine will 
prevent
that from happening.

There was an attempt to convert namespaces_rwsem a srcu, but my comment to
that was that this is an intrusive change for a complaint that we think 
is a false-positive.

Do you see a proper way to solve this? Would love to see a better 
solution here.

The original report is at:
https://lore.kernel.org/linux-block/20220930001943.zdbvolc3gkekfmcv@shindev/ 



  reply	other threads:[~2024-05-22 18:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22  9:15 [PATCH] nvme-pci: silence a lockdep complaint Sagi Grimberg
2024-05-22 12:18 ` Shinichiro Kawasaki
2024-05-22 16:12   ` Keith Busch
2024-05-22 16:28     ` Christoph Hellwig
2024-05-22 18:00       ` Sagi Grimberg [this message]
2024-05-22 21:36         ` Keith Busch
2024-05-23  6:54           ` Christoph Hellwig
2024-05-23 10:04             ` Sagi Grimberg
2024-05-23 12:39               ` Christoph Hellwig
2024-05-23 13:02                 ` Sagi Grimberg
2024-05-23 13:19                   ` Christoph Hellwig
2024-05-23 13:45                     ` Sagi Grimberg
2024-05-23 15:02                       ` Keith Busch
2024-05-23  8:06           ` Christoph Hellwig

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=a0657f0a-44af-4765-abe3-acc8a1017b40@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=shinichiro.kawasaki@wdc.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