From: Bob Pearson <rpearsonhpe@gmail.com>
To: Yanjun Zhu <yanjun.zhu@linux.dev>, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Jason Gunthorpe <jgg@nvidia.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Yi Zhang <yi.zhang@redhat.com>
Subject: Re: blktest failures
Date: Fri, 15 Apr 2022 02:29:13 -0500 [thread overview]
Message-ID: <faacdaa0-849b-e10f-7f27-f63bd203aaed@gmail.com> (raw)
In-Reply-To: <d594aef2-7728-d9f3-59eb-148a492ec8af@linux.dev>
On 4/15/22 02:12, Yanjun Zhu wrote:
> 在 2022/4/10 5:43, Bob Pearson 写道:
>> On 4/9/22 00:04, Christoph Hellwig wrote:
>>> On Fri, Apr 08, 2022 at 04:25:12PM -0700, Bart Van Assche wrote:
>>>> One of the functions in the above call stack is sd_remove(). sd_remove()
>>>> calls del_gendisk() just before calling sd_shutdown(). sd_shutdown()
>>>> submits the SYNCHRONIZE CACHE command. In del_gendisk() I found the
>>>> following comment: "Fail any new I/O". Do you agree that failing new I/O
>>>> before sd_shutdown() is called is wrong? Is there any other way to fix this
>>>> than moving the blk_queue_start_drain() etc. calls out of del_gendisk() and
>>>> into a new function?
>>>
>>> That SYNCHRONIZE CACHE is a passthrough command sent on the request_queue
>>> and should not be affected by stopping all file system I/O.
>>
>> When I run check -q srp
>> all the test cases pass but each one stops for 3+ minutes at synchronize cache.
>> The rxe device is still active until sync cache returns when the last QP and the PD
>> are destroyed. It may be that the queues are blocked waiting for something else
>> even though they have reported success??
>
> If you remove all the xarray patches and use the original source code. This will not occur.
>
> Zhu Yanjun
>
I missed one other point. The 3 minute delay is actually not a rxe bug at all but was recently
caused by a bad scsi patch which has since been reverted.
next prev parent reply other threads:[~2022-04-15 7:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 22:10 blktest failures Bob Pearson
2022-04-08 22:50 ` Bob Pearson
2022-04-08 23:25 ` Bart Van Assche
2022-04-09 0:31 ` Yi Zhang
2022-04-09 4:33 ` Bart Van Assche
2022-04-09 5:04 ` Christoph Hellwig
2022-04-09 21:43 ` Bob Pearson
2022-04-09 21:47 ` Bart Van Assche
2022-04-15 7:12 ` Yanjun Zhu
2022-04-15 7:26 ` Bob Pearson
2022-04-15 7:29 ` Bob Pearson [this message]
2022-04-15 7:37 ` Yanjun Zhu
2022-04-15 7:46 ` Bob Pearson
2022-04-15 7:59 ` Yanjun Zhu
2022-04-15 15:44 ` Bob Pearson
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=faacdaa0-849b-e10f-7f27-f63bd203aaed@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yanjun.zhu@linux.dev \
--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).