From: Chris Leech <cleech@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>, Yi Zhang <yi.zhang@redhat.com>,
linux-nvme@lists.infradead.org
Subject: Re: [bug report] WARNING: possible circular locking dependency detected with blktests nvme-tcp nvme/013
Date: Tue, 15 Feb 2022 07:18:17 -0800 [thread overview]
Message-ID: <03b33f30-aff7-84e4-8415-782d204177fe@redhat.com> (raw)
In-Reply-To: <e6062357-beb7-7150-1e88-1109babcb86a@redhat.com>
On 2/14/22 8:21 PM, Chris Leech wrote:
> Also, I might have a sleeping function called in atomic context report
> with a similar enough call trace to take a closer look at the direct send.
That looks to be a backport run with device mapper multipath, and a
repeat of the dm-rq BLK_MQ_F_BLOCKING discussion on linux-block.
I currently don't see a reason why the lockdep annotation wouldn't be
enough for this. I'll send a real patch if that's the way we want to go.
- Chris
next prev parent reply other threads:[~2022-02-15 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 11:20 [bug report] WARNING: possible circular locking dependency detected with blktests nvme-tcp nvme/013 Yi Zhang
2021-09-29 11:06 ` Sagi Grimberg
2022-02-11 5:38 ` Yi Zhang
2022-02-15 4:21 ` Chris Leech
2022-02-15 15:18 ` Chris Leech [this message]
2022-02-20 12:56 ` Sagi Grimberg
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=03b33f30-aff7-84e4-8415-782d204177fe@redhat.com \
--to=cleech@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--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).