public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Changhui Zhong <czhong@redhat.com>
Cc: Linux Block Devices <linux-block@vger.kernel.org>,
	io-uring@vger.kernel.org
Subject: Re: [bug report] WARNING: CPU: 3 PID: 175811 at io_uring/io_uring.c:2921 io_ring_exit_work+0x155/0x288
Date: Tue, 24 Jun 2025 16:03:40 +0800	[thread overview]
Message-ID: <aFpb3BjH4T8q8KAY@fedora> (raw)
In-Reply-To: <CAGVVp+UFKKb4ydw1+zWX9Bre6vt9TUFt9FY2qOx0LMv+8VaVoA@mail.gmail.com>

On Tue, Jun 24, 2025 at 01:37:55PM +0800, Changhui Zhong wrote:
> Hello,
> 
> the following warnning info was triggered by ubdsrv  generic/004 tests,
> please help check and let me know if you need any info/test, thanks.
> 
> repo: https://github.com/torvalds/linux.git
> branch: master
> INFO: HEAD of cloned kernel
> commit 86731a2a651e58953fc949573895f2fa6d456841
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Sun Jun 22 13:30:08 2025 -0700
> 
>     Linux 6.16-rc3
> 
> 
> reproducer:
> # echo 0 > /proc/sys/kernel/io_uring_disabled
> # modprobe ublk_drv
> # for i in {0..30};do make test T=generic; done

Hi Changhui,

Please try the fix for your yesterday's report:

https://lore.kernel.org/linux-block/20250624022049.825370-1-ming.lei@redhat.com/

The same test can survive for hours in my VM with the fix.


Thanks,
Ming


  parent reply	other threads:[~2025-06-24  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24  5:37 [bug report] WARNING: CPU: 3 PID: 175811 at io_uring/io_uring.c:2921 io_ring_exit_work+0x155/0x288 Changhui Zhong
2025-06-24  5:53 ` Changhui Zhong
2025-06-24  8:03 ` Ming Lei [this message]
2025-06-24 15:02   ` Changhui Zhong

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=aFpb3BjH4T8q8KAY@fedora \
    --to=ming.lei@redhat.com \
    --cc=czhong@redhat.com \
    --cc=io-uring@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox