From: Sagi Grimberg <sagi@grimberg.me>
To: Yi Zhang <yi.zhang@redhat.com>, Chao Leng <lengchao@huawei.com>,
Ming Lei <ming.lei@redhat.com>
Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2 0/5] avoid race for time out
Date: Thu, 29 Oct 2020 14:00:41 -0700 [thread overview]
Message-ID: <e913e433-d8ef-c04b-d9fa-3a6d71657136@grimberg.me> (raw)
In-Reply-To: <aba13cb9-a3d4-490b-4d1d-1deb60eafff6@redhat.com>
> 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.
For debug purposes, can you switch to run blktests with siw for
comparison?
This patch set should move forward for inclusion regardless.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-10-29 21:00 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 [this message]
2020-10-29 21:01 ` Sagi Grimberg
2020-10-30 0:04 ` Yi Zhang
2020-10-30 1:00 ` Ming Lei
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=e913e433-d8ef-c04b-d9fa-3a6d71657136@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.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).