lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6802834a.050a0220.243d89.001f.GAE@google.com>
Date: Fri, 18 Apr 2025 09:52:26 -0700
From: syzbot <syzbot+47e57fb1309cf7e8d1bc@...kaller.appspotmail.com>
To: dakr@...nel.org, gregkh@...uxfoundation.org, len.brown@...el.com, 
	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, pavel@...nel.org, 
	rafael@...nel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [pm?] WARNING in complete_all

Hello,

syzbot found the following issue on:

HEAD commit:    8ffd015db85f Linux 6.15-rc2
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=125920cc580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=104a680cd89f1ed7
dashboard link: https://syzkaller.appspot.com/bug?extid=47e57fb1309cf7e8d1bc
compiler:       aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-8ffd015d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/54631d1d74e9/vmlinux-8ffd015d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1d54de8b3f30/Image-8ffd015d.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+47e57fb1309cf7e8d1bc@...kaller.appspotmail.com

------------[ cut here ]------------
Not in threaded context on PREEMPT_RT as expected
WARNING: CPU: 1 PID: 4317 at kernel/sched/completion.c:71 complete_all+0x1a4/0x1e4 kernel/sched/completion.c:71
Modules linked in:
CPU: 1 UID: 0 PID: 4317 Comm: kworker/u8:6 Not tainted 6.15.0-rc2-syzkaller #0 PREEMPT 
Hardware name: linux,dummy-virt (DT)
Workqueue: netns cleanup_net
pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : complete_all+0x1a4/0x1e4 kernel/sched/completion.c:71
lr : complete_all+0x1a4/0x1e4 kernel/sched/completion.c:71
sp : ffff8000a2727630
x29: ffff8000a2727630 x28: 1fffe00003ac34ff x27: ffff00001d61a7fc
x26: ffff00001d61aaf0 x25: ffff00000f4c5000 x24: 0000000000000000
x23: 0000000004208060 x22: 1ffff000144e4ee8 x21: ffff7fffe309e000
x20: ffff000017580000 x19: ffff00001d61a858 x18: ffff80008d90745c
x17: ffff80008703efc0 x16: 1fffe0000d41bb38 x15: dfff800000000000
x14: ffff00006a0c85b0 x13: 0000000000000000 x12: ffff7000144e4e33
x11: 1ffff000144e4e32 x10: ffff7000144e4e32 x9 : dfff800000000000
x8 : ffff8000a2727198 x7 : ffff8000a27272a0 x6 : ffff8000a27271f0
x5 : ffff8000a27271d8 x4 : 0000000000000004 x3 : 1fffe0000d41ad55
x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000017580000
Call trace:
 complete_all+0x1a4/0x1e4 kernel/sched/completion.c:71 (P)
 device_pm_remove+0x5c/0x2cc drivers/base/power/main.c:157
 device_del+0x2d8/0x7b4 drivers/base/core.c:3856
 netdev_unregister_kobject+0x230/0x408 net/core/net-sysfs.c:2308
 unregister_netdevice_many_notify+0xd84/0x1af4 net/core/dev.c:12007
 unregister_netdevice_many+0x18/0x24 net/core/dev.c:12035
 cleanup_net+0x408/0x93c net/core/net_namespace.c:649
 process_one_work+0x7cc/0x18d4 kernel/workqueue.c:3238
 process_scheduled_works kernel/workqueue.c:3319 [inline]
 worker_thread+0x734/0xb84 kernel/workqueue.c:3400
 kthread+0x348/0x5fc kernel/kthread.c:464
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
irq event stamp: 747794
hardirqs last  enabled at (747793): [<ffff80008024b4fc>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1525 [inline]
hardirqs last  enabled at (747793): [<ffff80008024b4fc>] finish_lock_switch kernel/sched/core.c:5130 [inline]
hardirqs last  enabled at (747793): [<ffff80008024b4fc>] finish_task_switch.isra.0+0x1a8/0x854 kernel/sched/core.c:5248
hardirqs last disabled at (747794): [<ffff80008543cc18>] el1_dbg+0x24/0x9c arch/arm64/kernel/entry-common.c:488
softirqs last  enabled at (747746): [<ffff8000801b6c08>] softirq_handle_end kernel/softirq.c:425 [inline]
softirqs last  enabled at (747746): [<ffff8000801b6c08>] handle_softirqs+0x88c/0xdb4 kernel/softirq.c:607
softirqs last disabled at (747729): [<ffff800080010760>] __do_softirq+0x14/0x20 kernel/softirq.c:613
---[ end trace 0000000000000000 ]---
bond0 (unregistering): (slave bond_slave_0): Releasing backup interface
bond0 (unregistering): (slave bond_slave_1): Releasing backup interface
bond0 (unregistering): Released all slaves
bond1 (unregistering): Released all slaves
hsr_slave_0: left promiscuous mode
hsr_slave_1: left promiscuous mode
veth1_macvtap: left promiscuous mode
veth0_macvtap: left promiscuous mode
veth1_vlan: left promiscuous mode
veth0_vlan: left promiscuous mode
netdevsim netdevsim1 netdevsim3 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0
netdevsim netdevsim1 netdevsim2 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0
netdevsim netdevsim1 netdevsim1 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0
netdevsim netdevsim1 netdevsim0 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0
bond0 (unregistering): (slave bond_slave_0): Releasing backup interface
bond0 (unregistering): (slave bond_slave_1): Releasing backup interface
bond0 (unregistering): Released all slaves
hsr_slave_0: left promiscuous mode
hsr_slave_1: left promiscuous mode
veth1_macvtap: left promiscuous mode
veth0_macvtap: left promiscuous mode
veth1_vlan: left promiscuous mode
veth0_vlan: left promiscuous mode


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ