All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<io-uring@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
	<linux-kernel@vger.kernel.org>,
	"Caleb Sander Mateos" <csander@purestorage.com>,
	<oliver.sang@intel.com>
Subject: Re: [PATCH v3 4/4] io_uring: avoid uring_lock for IORING_SETUP_SINGLE_ISSUER
Date: Thu, 27 Nov 2025 13:55:35 +0800	[thread overview]
Message-ID: <202511270630.4e038598-lkp@intel.com> (raw)
In-Reply-To: <20251125233928.3962947-5-csander@purestorage.com>



Hello,

kernel test robot noticed "WARNING:at_io_uring/io_uring.h:#io_ring_ctx_wait_and_kill" on:

commit: f82bff8359e8780d831f1180c9e8196d2d20f03c ("[PATCH v3 4/4] io_uring: avoid uring_lock for IORING_SETUP_SINGLE_ISSUER")
url: https://github.com/intel-lab-lkp/linux/commits/Caleb-Sander-Mateos/io_uring-clear-IORING_SETUP_SINGLE_ISSUER-for-IORING_SETUP_SQPOLL/20251126-074303
base: https://git.kernel.org/cgit/linux/kernel/git/axboe/linux.git for-next
patch link: https://lore.kernel.org/all/20251125233928.3962947-5-csander@purestorage.com/
patch subject: [PATCH v3 4/4] io_uring: avoid uring_lock for IORING_SETUP_SINGLE_ISSUER

in testcase: trinity
version: 
with following parameters:

	runtime: 300s
	group: group-01
	nr_groups: 5



config: x86_64-kexec
compiler: clang-20
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G

(please refer to attached dmesg/kmsg for entire log/backtrace)



If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202511270630.4e038598-lkp@intel.com


[   22.144951][ T6341] ------------[ cut here ]------------
[   22.145674][ T1564] [main] futex: 0 owner:0
[   22.146000][ T6341] WARNING: CPU: 1 PID: 6341 at io_uring/io_uring.h:266 io_ring_ctx_wait_and_kill (io_uring/io_uring.h:266)
[   22.146149][ T1564]
[   22.146482][ T6341] Modules linked in:
[   22.147631][ T1564] [main] futex: 0 owner:0
[   22.147751][ T6341]  can_bcm
[   22.148030][ T1564]
[   22.148330][ T6341]  can_raw
[   22.148974][ T1564] [main] futex: 0 owner:0
[   22.149038][ T6341]  can
[   22.149264][ T1564]
[   22.149572][ T6341]  cn scsi_transport_iscsi sr_mod cdrom
[   22.149579][ T6341] CPU: 1 UID: 65534 PID: 6341 Comm: trinity-c3 Not tainted 6.18.0-rc6-00278-gf82bff8359e8 #1 PREEMPT(voluntary)
[   22.149582][ T6341] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[   22.151109][ T1564] [main] Reserved/initialized 10 futexes.
[   22.151645][ T6341] RIP: 0010:io_ring_ctx_wait_and_kill (io_uring/io_uring.h:266)
[   22.152382][ T1564]
[   22.152774][ T6341] Code: 02 00 00 e8 af e2 0b 00 65 48 8b 05 97 1a 5f 02 48 3b 44 24 48 0f 85 98 00 00 00 48 83 c4 50 5b 41 5e 41 5f e9 be c6 f8 00 cc <0f> 0b e9 ed fe ff ff 31 c0 4c 8d 7c 24 28 49 89 47 18 49 89 47 10
All code
========
   0:	02 00                	add    (%rax),%al
   2:	00 e8                	add    %ch,%al
   4:	af                   	scas   %es:(%rdi),%eax
   5:	e2 0b                	loop   0x12
   7:	00 65 48             	add    %ah,0x48(%rbp)
   a:	8b 05 97 1a 5f 02    	mov    0x25f1a97(%rip),%eax        # 0x25f1aa7
  10:	48 3b 44 24 48       	cmp    0x48(%rsp),%rax
  15:	0f 85 98 00 00 00    	jne    0xb3
  1b:	48 83 c4 50          	add    $0x50,%rsp
  1f:	5b                   	pop    %rbx
  20:	41 5e                	pop    %r14
  22:	41 5f                	pop    %r15
  24:	e9 be c6 f8 00       	jmp    0xf8c6e7
  29:	cc                   	int3
  2a:*	0f 0b                	ud2		<-- trapping instruction
  2c:	e9 ed fe ff ff       	jmp    0xffffffffffffff1e
  31:	31 c0                	xor    %eax,%eax
  33:	4c 8d 7c 24 28       	lea    0x28(%rsp),%r15
  38:	49 89 47 18          	mov    %rax,0x18(%r15)
  3c:	49 89 47 10          	mov    %rax,0x10(%r15)

Code starting with the faulting instruction
===========================================
   0:	0f 0b                	ud2
   2:	e9 ed fe ff ff       	jmp    0xfffffffffffffef4
   7:	31 c0                	xor    %eax,%eax
   9:	4c 8d 7c 24 28       	lea    0x28(%rsp),%r15
   e:	49 89 47 18          	mov    %rax,0x18(%r15)
  12:	49 89 47 10          	mov    %rax,0x10(%r15)
[   22.154288][ T1564] [main] sysv_shm: id:0 size:40960 flags:7b0 ptr:(nil)
[   22.155063][ T6341] RSP: 0018:ffffc90000217db0 EFLAGS: 00010246
[   22.155249][ T1564]
[   22.155714][ T6341]
[   22.157177][ T1564] [main] sysv_shm: id:1 size:4096 flags:17b0 ptr:(nil)
[   22.157242][ T6341] RAX: 0000000000000000 RBX: ffff88810d435800 RCX: 0000000000000001
[   22.157489][ T1564]
[   22.157954][ T6341] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88810d435800
[   22.159286][ T1564] [main] Added 28 filenames from /dev
[   22.159684][ T6341] RBP: 00000000fffffff2 R08: 0000000000000000 R09: ffffffff00000000
[   22.159688][ T6341] R10: 0000000000000010 R11: 0000000000100000 R12: 0000000000000000
[   22.160050][ T1564]
[   22.160414][ T6341] R13: 0000000000000000 R14: 0000000000000000 R15: ffff888119bf9000
[   22.161762][ T1564] [main] Added 17230 filenames from /proc
[   22.161924][ T6341] FS:  00000000010a2880(0000) GS:ffff88889c519000(0000) knlGS:0000000000000000
[   22.162568][ T1564]
[   22.162958][ T6341] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   22.164372][ T1564] [main] Added 15134 filenames from /sys
[   22.164448][ T6341] CR2: 0000000000000008 CR3: 0000000165c9c000 CR4: 00000000000406f0
[   22.164456][ T6341] Call Trace:
[   22.164626][ T1564]
[   22.166367][ T6341]  <TASK>
[   22.168128][ T1564] [main] Couldn't open socket (30:1:0). Address family not supported by protocol
[   22.168186][ T6341]  io_uring_create (io_uring/io_uring.c:?)
[   22.168352][ T1564]
[   22.168974][ T6341]  __x64_sys_io_uring_setup (io_uring/io_uring.c:3766)
[   22.170902][ T1564] [main] Couldn't open socket (27:1:3). Address family not supported by protocol
[   22.172459][ T6341]  do_syscall_64 (arch/x86/entry/syscall_64.c:?)
[   22.172512][ T1564]
[   22.173163][ T6341]  ? exc_page_fault (arch/x86/include/asm/irqflags.h:37 arch/x86/include/asm/irqflags.h:114 arch/x86/mm/fault.c:1484 arch/x86/mm/fault.c:1532)
[   22.175090][ T1564] [main] Couldn't open socket (44:3:0). Address family not supported by protocol
[   22.175097][ T6341]  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
[   22.175309][ T1564]
[   22.175935][ T6341] RIP: 0033:0x453b29
[   22.176865][ T1564] Can't do protocol NETBEUI
[   22.176935][ T6341] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 3b 84 00 00 c3 66 2e 0f 1f 84 00 00 00 00
All code
========
   0:	00 f3                	add    %dh,%bl
   2:	c3                   	ret
   3:	66 2e 0f 1f 84 00 00 	cs nopw 0x0(%rax,%rax,1)
   a:	00 00 00 
   d:	0f 1f 40 00          	nopl   0x0(%rax)
  11:	48 89 f8             	mov    %rdi,%rax
  14:	48 89 f7             	mov    %rsi,%rdi
  17:	48 89 d6             	mov    %rdx,%rsi
  1a:	48 89 ca             	mov    %rcx,%rdx
  1d:	4d 89 c2             	mov    %r8,%r10
  20:	4d 89 c8             	mov    %r9,%r8
  23:	4c 8b 4c 24 08       	mov    0x8(%rsp),%r9
  28:	0f 05                	syscall
  2a:*	48 3d 01 f0 ff ff    	cmp    $0xfffffffffffff001,%rax		<-- trapping instruction
  30:	0f 83 3b 84 00 00    	jae    0x8471
  36:	c3                   	ret
  37:	66                   	data16
  38:	2e                   	cs
  39:	0f                   	.byte 0xf
  3a:	1f                   	(bad)
  3b:	84 00                	test   %al,(%rax)
  3d:	00 00                	add    %al,(%rax)
	...

Code starting with the faulting instruction
===========================================
   0:	48 3d 01 f0 ff ff    	cmp    $0xfffffffffffff001,%rax
   6:	0f 83 3b 84 00 00    	jae    0x8447
   c:	c3                   	ret
   d:	66                   	data16
   e:	2e                   	cs
   f:	0f                   	.byte 0xf
  10:	1f                   	(bad)
  11:	84 00                	test   %al,(%rax)
  13:	00 00                	add    %al,(%rax)


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251127/202511270630.4e038598-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  reply	other threads:[~2025-11-27  5:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 23:39 [PATCH v3 0/4] io_uring: avoid uring_lock for IORING_SETUP_SINGLE_ISSUER Caleb Sander Mateos
2025-11-25 23:39 ` [PATCH v3 1/4] io_uring: clear IORING_SETUP_SINGLE_ISSUER for IORING_SETUP_SQPOLL Caleb Sander Mateos
2025-11-25 23:39 ` [PATCH v3 2/4] io_uring: use io_ring_submit_lock() in io_iopoll_req_issued() Caleb Sander Mateos
2025-11-25 23:39 ` [PATCH v3 3/4] io_uring: factor out uring_lock helpers Caleb Sander Mateos
2025-11-25 23:39 ` [PATCH v3 4/4] io_uring: avoid uring_lock for IORING_SETUP_SINGLE_ISSUER Caleb Sander Mateos
2025-11-27  5:55   ` kernel test robot [this message]
2025-11-26  8:15 ` [syzbot ci] " syzbot ci
2025-11-26 17:30   ` Caleb Sander Mateos

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=202511270630.4e038598-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    /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.