| 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
| ||
|
Message-ID: <00000000000033d3ce0620250e5f@google.com> Date: Tue, 20 Aug 2024 15:36:24 -0700 From: syzbot <syzbot+d0b64fece0a7107b3761@...kaller.appspotmail.com> To: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com Subject: [syzbot] [kernel?] WARNING: locking bug in sched_ttwu_pending Hello, syzbot found the following issue on: HEAD commit: 670c12ce09a8 Merge tag 'for-6.11/dm-fixes' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=138e5bd3980000 kernel config: https://syzkaller.appspot.com/x/.config?x=7229118d88b4a71b dashboard link: https://syzkaller.appspot.com/bug?extid=d0b64fece0a7107b3761 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/2c3073329e9b/disk-670c12ce.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/d8cf388cb086/vmlinux-670c12ce.xz kernel image: https://storage.googleapis.com/syzbot-assets/f8bfb3cf4d1a/bzImage-670c12ce.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+d0b64fece0a7107b3761@...kaller.appspotmail.com ------------[ cut here ]------------ DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:231 hlock_class kernel/locking/lockdep.c:231 [inline] WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:231 check_wait_context kernel/locking/lockdep.c:4772 [inline] WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:231 __lock_acquire+0x58c/0x2040 kernel/locking/lockdep.c:5092 Modules linked in: CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.11.0-rc3-syzkaller-00221-g670c12ce09a8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 RIP: 0010:hlock_class kernel/locking/lockdep.c:231 [inline] RIP: 0010:check_wait_context kernel/locking/lockdep.c:4772 [inline] RIP: 0010:__lock_acquire+0x58c/0x2040 kernel/locking/lockdep.c:5092 Code: 00 00 83 3d 75 2d a8 0e 00 75 23 90 48 c7 c7 00 d4 0a 8c 48 c7 c6 a0 d6 0a 8c e8 4f d8 e5 ff 48 ba 00 00 00 00 00 fc ff df 90 <0f> 0b 90 90 90 31 db 48 81 c3 c4 00 00 00 48 89 d8 48 c1 e8 03 0f RSP: 0018:ffffc90000a18b90 EFLAGS: 00010046 RAX: 3292b9acfb26c100 RBX: 0000000000001cd8 RCX: ffff8880182f0000 RDX: dffffc0000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000000 R08: ffffffff8155b4d2 R09: 1ffff1101726519a R10: dffffc0000000000 R11: ffffed101726519b R12: ffff8880182f0000 R13: 0000000000001cd8 R14: 1ffff1100305e160 R15: ffff8880182f0b00 FS: 0000000000000000(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020028000 CR3: 000000005d072000 CR4: 0000000000350ef0 Call Trace: <IRQ> lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759 _raw_spin_lock_nested+0x31/0x40 kernel/locking/spinlock.c:378 raw_spin_rq_lock_nested+0xb0/0x140 kernel/sched/core.c:568 raw_spin_rq_lock kernel/sched/sched.h:1415 [inline] _raw_spin_rq_lock_irqsave kernel/sched/sched.h:1435 [inline] rq_lock_irqsave kernel/sched/sched.h:1700 [inline] sched_ttwu_pending+0x182/0x740 kernel/sched/core.c:3674 csd_do_func kernel/smp.c:134 [inline] __flush_smp_call_function_queue+0x1146/0x1690 kernel/smp.c:559 __sysvec_call_function_single+0xb8/0x430 arch/x86/kernel/smp.c:271 instr_sysvec_call_function_single arch/x86/kernel/smp.c:266 [inline] sysvec_call_function_single+0x9e/0xc0 arch/x86/kernel/smp.c:266 </IRQ> <TASK> asm_sysvec_call_function_single+0x1a/0x20 arch/x86/include/asm/idtentry.h:709 RIP: 0010:native_irq_disable arch/x86/include/asm/irqflags.h:37 [inline] RIP: 0010:arch_local_irq_disable arch/x86/include/asm/irqflags.h:92 [inline] RIP: 0010:acpi_safe_halt+0x21/0x30 drivers/acpi/processor_idle.c:112 Code: 90 90 90 90 90 90 90 90 90 65 48 8b 04 25 40 d7 03 00 48 f7 00 08 00 00 00 75 10 eb 07 0f 00 2d 95 4b b3 00 f3 0f 1e fa fb f4 <fa> e9 d4 6f 39 00 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 RSP: 0018:ffffc900001a7d08 EFLAGS: 00000246 RAX: ffff8880182f0000 RBX: ffff88801daa8864 RCX: 0000000001aa1b61 RDX: 0000000000000001 RSI: ffff88801daa8800 RDI: ffff88801daa8864 RBP: 000000000003a6b8 R08: ffff8880b9337c7b R09: 1ffff11017266f8f R10: dffffc0000000000 R11: ffffffff8bb6cce0 R12: ffff8880167e6800 R13: 0000000000000000 R14: 0000000000000001 R15: ffffffff8f0dd380 acpi_idle_enter+0xe4/0x140 drivers/acpi/processor_idle.c:702 cpuidle_enter_state+0x114/0x480 drivers/cpuidle/cpuidle.c:267 cpuidle_enter+0x5d/0xa0 drivers/cpuidle/cpuidle.c:388 call_cpuidle kernel/sched/idle.c:155 [inline] cpuidle_idle_call kernel/sched/idle.c:230 [inline] do_idle+0x375/0x5d0 kernel/sched/idle.c:326 cpu_startup_entry+0x42/0x60 kernel/sched/idle.c:424 start_secondary+0x100/0x100 arch/x86/kernel/smpboot.c:313 common_startup_64+0x13e/0x147 </TASK> ---------------- Code disassembly (best guess): 0: 90 nop 1: 90 nop 2: 90 nop 3: 90 nop 4: 90 nop 5: 90 nop 6: 90 nop 7: 90 nop 8: 90 nop 9: 65 48 8b 04 25 40 d7 mov %gs:0x3d740,%rax 10: 03 00 12: 48 f7 00 08 00 00 00 testq $0x8,(%rax) 19: 75 10 jne 0x2b 1b: eb 07 jmp 0x24 1d: 0f 00 2d 95 4b b3 00 verw 0xb34b95(%rip) # 0xb34bb9 24: f3 0f 1e fa endbr64 28: fb sti 29: f4 hlt * 2a: fa cli <-- trapping instruction 2b: e9 d4 6f 39 00 jmp 0x397004 30: 66 0f 1f 84 00 00 00 nopw 0x0(%rax,%rax,1) 37: 00 00 39: 90 nop 3a: 90 nop 3b: 90 nop 3c: 90 nop 3d: 90 nop 3e: 90 nop 3f: 90 nop --- 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