From: Bjorn Helgaas <helgaas@kernel.org>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Yi Zhang <yi.zhang@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"mstowe@redhat.com" <mstowe@redhat.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Xiao Yang <yangx.jy@fujitsu.com>, Keith Busch <kbusch@kernel.org>
Subject: Re: blktests failures with v5.19-rc1
Date: Thu, 29 Dec 2022 12:13:34 -0600 [thread overview]
Message-ID: <20221229181334.GA616694@bhelgaas> (raw)
In-Reply-To: <20221219112703.rlqdo33ncgmuowfm@shindev>
On Mon, Dec 19, 2022 at 11:27:03AM +0000, Shinichiro Kawasaki wrote:
> Bjorn, FYI. This lockdep warning disappeared with kernel version
> v6.1. I bisected and found the commit 2d7f9f8c1815 ("kernfs: Improve
> kernfs_drain() and always call on removal.") avoided the issue. This
> commit touches kernfs_drain() and __kernfs_remove(), and modifies
> the condition to lock kernfs_rwsem. I think it explains why the
> lockdep disappeared. No longer need to work on this issue :)
Thanks for following up on this!
Bjorn
prev parent reply other threads:[~2022-12-29 18:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220609235329.4jbz4wr3eg2nmzqa@shindev>
[not found] ` <717734c9-c633-fb48-499e-7e3e15113020@nvidia.com>
[not found] ` <19d09611-42cc-5a81-d676-c5375865c14c@nvidia.com>
[not found] ` <20220610122517.6pt5y63hcosk5mes@shindev>
[not found] ` <YqNZiMw+rH5gyZDI@kbusch-mbp.dhcp.thefacebook.com>
[not found] ` <CAHj4cs9G0WDrnSS6iVZJfgfOcRR0ysJhw+9yqcbqE=_8mkF0zw@mail.gmail.com>
2022-06-14 1:09 ` blktests failures with v5.19-rc1 Shinichiro Kawasaki
2022-06-14 2:23 ` Keith Busch
2022-06-14 2:38 ` Chaitanya Kulkarni
2022-06-14 4:00 ` Shinichiro Kawasaki
2022-06-15 19:47 ` Bjorn Helgaas
2022-06-15 22:01 ` Chaitanya Kulkarni
2022-06-15 23:13 ` Yi Zhang
2022-06-16 4:42 ` Shinichiro Kawasaki
2022-06-16 17:55 ` Chaitanya Kulkarni
2022-06-15 23:16 ` Keith Busch
2022-07-19 4:50 ` Shinichiro Kawasaki
2022-07-19 22:31 ` Bjorn Helgaas
2022-07-20 2:27 ` Shinichiro Kawasaki
2022-12-19 11:27 ` Shinichiro Kawasaki
2022-12-29 18:13 ` Bjorn Helgaas [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=20221229181334.GA616694@bhelgaas \
--to=helgaas@kernel.org \
--cc=chaitanyak@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mstowe@redhat.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yangx.jy@fujitsu.com \
--cc=yi.zhang@redhat.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;
as well as URLs for NNTP newsgroup(s).