linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Yi Zhang <yi.zhang@redhat.com>, linux-nvme@lists.infradead.org
Subject: Re: [bug report] WARNING: inconsistent lock state observed with blktests nvme-tcp/003
Date: Sun, 21 Mar 2021 00:07:37 -0700	[thread overview]
Message-ID: <f1d1cda8-e2ec-800d-89ef-a3690262f21a@grimberg.me> (raw)
In-Reply-To: <1378655048.19877042.1616170706639.JavaMail.zimbra@redhat.com>

Thanks for reporting Yi,

I think I understand what is going on here.. blktests are
special in the sense that they run nvme-tcp and nvmet-tcp
on the same system, and since they have causal relationships
it makes sense how this can trigger.

Let me submit a couple of patches for this one...

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

      reply	other threads:[~2021-03-21  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1608490616.19876870.1616170480157.JavaMail.zimbra@redhat.com>
2021-03-19 16:18 ` [bug report] WARNING: inconsistent lock state observed with blktests nvme-tcp/003 Yi Zhang
2021-03-21  7:07   ` Sagi Grimberg [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=f1d1cda8-e2ec-800d-89ef-a3690262f21a@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=linux-nvme@lists.infradead.org \
    --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).