linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, axboe@fb.com,
	Chao Leng <lengchao@huawei.com>,
	kbusch@kernel.org, hch@lst.de
Subject: Re: [PATCH v2 0/5] avoid race for time out
Date: Fri, 30 Oct 2020 09:00:59 +0800	[thread overview]
Message-ID: <20201030010059.GB2012749@T590> (raw)
In-Reply-To: <eb2dcbb9-241f-e876-e914-3159f64b7351@redhat.com>

On Fri, Oct 30, 2020 at 08:04:07AM +0800, Yi Zhang wrote:
> 
> 
> On 10/30/20 5:00 AM, Sagi Grimberg wrote:
> > 
> > > Hello
> > > 
> > > This series fixed the WARNING issue I reported [1], but now the
> > > nvme/012 [2] will be hang there and never finished, here is the
> > > log[3]
> > > [1]
> > > https://lore.kernel.org/linux-nvme/1934331639.3314730.1602152202454.JavaMail.zimbra@redhat.com/
> > > 
> > > 
> > > [2]
> > > [root@hpe-xw9400-02 blktests]# nvme_trtype=tcp ./check nvme/012
> > > nvme/012 (run mkfs and data verification fio job on NVMeOF block
> > > device-backed ns)
> > >      runtime  1199.651s  ...
> > 
> > Hey Yi,
> > 
> > This is a different issue, as I said, first of all the test is not
> > designed to trigger this scenario so it is weird why it even happens.
> > 
> OK, I will keep monitor the issue in the future, and the original issue also
> found in stable branch, should we also CC stable?
> 
> Hi Ming
> 
> just FYI, with your path on top of this series
> the test passed 100 times although there are timeout, but finally
> reconnected and test finished.

Hi Yi,

Thanks for your test, I will re-post the patch out in linux-block today. 


Thanks,
Ming


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

      reply	other threads:[~2020-10-30  1:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  2:14 [PATCH v2 0/5] avoid race for time out Chao Leng
2020-10-28 11:36 ` Yi Zhang
2020-10-28 13:25   ` Ming Lei
2020-10-29  6:13   ` Chao Leng
2020-10-29 21:00   ` Sagi Grimberg
2020-10-29 21:01     ` Sagi Grimberg
2020-10-30  0:04     ` Yi Zhang
2020-10-30  1:00       ` 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=20201030010059.GB2012749@T590 \
    --to=ming.lei@redhat.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=lengchao@huawei.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).