From: Ming Lei <ming.lei@redhat.com>
To: Changhui Zhong <czhong@redhat.com>, Jens Axboe <axboe@kernel.dk>
Cc: Linux Block Devices <linux-block@vger.kernel.org>, ming.lei@redhat.com
Subject: Re: [bug report] WARNING: CPU: 5 PID: 679 at io_uring/io_uring.c:2835 io_ring_exit_work+0x2b6/0x2e0
Date: Tue, 16 Apr 2024 18:00:41 +0800 [thread overview]
Message-ID: <Zh5MSQVk54tN7Xx4@fedora> (raw)
In-Reply-To: <CAGVVp+X81FhOHH0E3BwcsVBYsAAOoAPXpTX5D_BbRH4jqjeTJg@mail.gmail.com>
On Tue, Apr 16, 2024 at 10:26:16AM +0800, Changhui Zhong wrote:
> > >
> > > I can't reproduce this here, fwiw. Ming, something you've seen?
> >
> > I just test against the latest for-next/block(-rc4 based), and still can't
> > reproduce it. There was such RH internal report before, and maybe not
> > ublk related.
> >
> > Changhui, if the issue can be reproduced in your machine, care to share
> > your machine for me to investigate a bit?
> >
> > Thanks,
> > Ming
> >
>
> I still can reproduce this issue on my machine，
> and I shared machine to Ming，he can do more investigation for this issue，
>
> [ 1244.207092] running generic/006
> [ 1246.456896] blk_print_req_error: 77 callbacks suppressed
> [ 1246.456907] I/O error, dev ublkb1, sector 2395864 op 0x1:(WRITE)
> flags 0x8800 phys_seg 1 prio class 0
The failure is actually triggered in recovering qcow2 target in generic/005,
since ublkb0 isn't removed successfully in generic/005.
git-bisect shows that the 1st bad commit is cca6571381a0 ("io_uring/rw:
cleanup retry path").
And not see any issue in uring command side, so the trouble seems
in normal io_uring rw side over XFS file, and not related with block
device.
Thanks,
Ming
next prev parent reply other threads:[~2024-04-16 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 9:14 [bug report] WARNING: CPU: 5 PID: 679 at io_uring/io_uring.c:2835 io_ring_exit_work+0x2b6/0x2e0 Changhui Zhong
2024-04-15 14:28 ` Jens Axboe
2024-04-16 1:25 ` Ming Lei
2024-04-16 2:26 ` Changhui Zhong
2024-04-16 10:00 ` Ming Lei [this message]
2024-04-16 11:38 ` Jens Axboe
2024-04-16 12:14 ` Pavel Begunkov
2024-04-16 12:24 ` Jens Axboe
2024-04-16 12:40 ` Pavel Begunkov
2024-04-16 12:51 ` Jens Axboe
2024-04-16 13:08 ` Pavel Begunkov
2024-04-16 12:35 ` Jens Axboe
2024-04-16 12:53 ` 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=Zh5MSQVk54tN7Xx4@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=czhong@redhat.com \
--cc=linux-block@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.