All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Changhui Zhong <czhong@redhat.com>,
	Linux Block Devices <linux-block@vger.kernel.org>
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 09:25:34 +0800	[thread overview]
Message-ID: <Zh3TjqD1763LzXUj@fedora> (raw)
In-Reply-To: <06b1c052-cbd4-4b8c-bc58-175fe6d41d72@kernel.dk>

On Mon, Apr 15, 2024 at 08:28:05AM -0600, Jens Axboe wrote:
> On 4/15/24 3:14 AM, Changhui Zhong wrote:
> > Hello,
> > 
> > repo:https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
> > branch:for-next
> > commit HEAD:f2738f2440eb573094ef6f09cca915ae37f2f8bc
> > 
> > hit this issue on recent upstream,reproduced with ubdsrv, trigger this
> > issue on "running generic/005" and "running generic/006",
> > 
> > # cd ubdsrv
> > # make test T=generic
> > 
> > [  993.347470] WARNING: CPU: 13 PID: 4628 at io_uring/io_uring.c:2835
> > io_ring_exit_work+0x2b6/0x2e0
> > [  993.357304] Modules linked in: ext4 mbcache jbd2 rfkill sunrpc
> > dm_multipath intel_rapl_msr intel_rapl_common intel_uncore_frequency
> > intel_uncore_frequency_common i10nm_edac nfit libnvdimm
> > x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ipmi_ssif
> > rapl intel_cstate mgag200 iTCO_wdt dax_hmem iTCO_vendor_support
> > cxl_acpi mei_me i2c_algo_bit cxl_core i2c_i801 drm_shmem_helper
> > isst_if_mmio isst_if_mbox_pci drm_kms_helper intel_uncore mei einj
> > ioatdma pcspkr i2c_smbus isst_if_common intel_vsec intel_pch_thermal
> > ipmi_si dca ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter drm
> > fuse xfs libcrc32c sd_mod t10_pi sg ahci crct10dif_pclmul libahci
> > crc32_pclmul crc32c_intel libata tg3 ghash_clmulni_intel wmi dm_mirror
> > dm_region_hash dm_log dm_mod
> > [  993.431516] CPU: 13 PID: 4628 Comm: kworker/u96:2 Not tainted 6.9.0-rc3+ #1
> > [  993.439297] Hardware name: Lenovo ThinkSystem SR650 V2/7Z73CTO1WW,
> > BIOS AFE120G-1.40 09/20/2022
> > [  993.449015] Workqueue: iou_exit io_ring_exit_work
> > [  993.454275] RIP: 0010:io_ring_exit_work+0x2b6/0x2e0
> > [  993.459729] Code: 89 e7 e8 6d de ff ff 48 8b 44 24 58 65 48 2b 04
> > 25 28 00 00 00 75 2e 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc
> > cc cc cc <0f> 0b 41 be 60 ea 00 00 e9 45 fe ff ff 0f 0b e9 1d ff ff ff
> > e8 c1
> > [  993.480695] RSP: 0018:ff70b0c247657dd0 EFLAGS: 00010287
> > [  993.486533] RAX: 00000001000a94c0 RBX: ff26a781c5b48448 RCX: 0000000000000000
> > [  993.494506] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ff26a781c5b48040
> > [  993.502475] RBP: ff70b0c247657e60 R08: 0000000000000000 R09: ffffffffbb254ca0
> > [  993.510445] R10: 0000000000000000 R11: 0000000000000000 R12: ff26a781c5b48000
> > [  993.518415] R13: ff26a781c5b48040 R14: 0000000000000032 R15: 0000000000000000
> > [  993.526387] FS:  0000000000000000(0000) GS:ff26a784efa80000(0000)
> > knlGS:0000000000000000
> > [  993.535427] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [  993.541848] CR2: 00007ff5a794f004 CR3: 000000003ea20006 CR4: 0000000000771ef0
> > [  993.549820] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > [  993.557790] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > [  993.565761] PKRU: 55555554
> > [  993.568787] Call Trace:
> > [  993.571523]  <TASK>
> > [  993.573871]  ? __warn+0x7f/0x130
> > [  993.577486]  ? io_ring_exit_work+0x2b6/0x2e0
> > [  993.582259]  ? report_bug+0x18a/0x1a0
> > [  993.586358]  ? handle_bug+0x3c/0x70
> > [  993.590262]  ? exc_invalid_op+0x14/0x70
> > [  993.594551]  ? asm_exc_invalid_op+0x16/0x20
> > [  993.599234]  ? io_ring_exit_work+0x2b6/0x2e0
> > [  993.604006]  ? try_to_wake_up+0x21e/0x600
> > [  993.608490]  process_one_work+0x193/0x3d0
> > [  993.612969]  worker_thread+0x2fc/0x410
> > [  993.617161]  ? __pfx_worker_thread+0x10/0x10
> > [  993.621934]  kthread+0xdc/0x110
> > [  993.625448]  ? __pfx_kthread+0x10/0x10
> > [  993.629640]  ret_from_fork+0x2d/0x50
> > [  993.633640]  ? __pfx_kthread+0x10/0x10
> > [  993.637830]  ret_from_fork_asm+0x1a/0x30
> > [  993.642219]  </TASK>
> > [  993.644661] ---[ end trace 0000000000000000 ]---
> 
> 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


  reply	other threads:[~2024-04-16  1:25 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 [this message]
2024-04-16  2:26     ` Changhui Zhong
2024-04-16 10:00       ` Ming Lei
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=Zh3TjqD1763LzXUj@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.