From: Ziyang Zhang <[email protected]>
To: Ming Lei <[email protected]>
Cc: [email protected], [email protected],
Xiaoguang Wang <[email protected]>,
Jens Axboe <[email protected]>
Subject: Re: [bug report] ublk_drv: hang while removing ublk character device
Date: Wed, 3 Aug 2022 20:04:01 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <YupjpIAQYxbuaOR6@T590>
On 2022/8/3 20:01, Ming Lei wrote:
> Hi Ziyang,
>
> On Wed, Aug 03, 2022 at 07:45:24PM +0800, Ziyang Zhang wrote:
>> Hi all,
>>
>> Now ublk_drv has been pushed into master branch and I am running tests on it.
>> With newest(master) kernel and newest(master) ublksrv[1], a test case(generic/001) of ublksrv failed(hanged):
>>
>
> Please see the fix:
>
> https://lore.kernel.org/io-uring/[email protected]/T/#t
Yeah, I got this. Thanks for the fix, Ming.
prev parent reply other threads:[~2022-08-03 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 11:45 [bug report] ublk_drv: hang while removing ublk character device Ziyang Zhang
2022-08-03 12:01 ` Ming Lei
2022-08-03 12:04 ` Ziyang Zhang [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=2edb5698-4423-cbdb-350b-609e8fba1e1c@linux.alibaba.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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