| 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: <0000000000008dfcc10619add74a@google.com> Date: Thu, 30 May 2024 08:51:36 -0700 From: syzbot <syzbot+07620ae683e780f6a943@...kaller.appspotmail.com> To: chandan.babu@...cle.com, djwong@...nel.org, linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org, syzkaller-bugs@...glegroups.com Subject: [syzbot] [xfs?] WARNING: locking bug in xfs_inode_mark_reclaimable Hello, syzbot found the following issue on: HEAD commit: c13320499ba0 Merge tag '6.10-rc-smb3-fixes-part2' of git:/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1237c344980000 kernel config: https://syzkaller.appspot.com/x/.config?x=e70c03a304f3c3ef dashboard link: https://syzkaller.appspot.com/bug?extid=07620ae683e780f6a943 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-c1332049.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/4d89011b261c/vmlinux-c1332049.xz kernel image: https://storage.googleapis.com/syzbot-assets/86f1a107597e/bzImage-c1332049.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+07620ae683e780f6a943@...kaller.appspotmail.com ------------[ cut here ]------------ DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 0 PID: 6275 at kernel/locking/lockdep.c:232 hlock_class kernel/locking/lockdep.c:232 [inline] WARNING: CPU: 0 PID: 6275 at kernel/locking/lockdep.c:232 hlock_class+0xfa/0x130 kernel/locking/lockdep.c:221 Modules linked in: CPU: 0 PID: 6275 Comm: syz-executor.2 Not tainted 6.9.0-syzkaller-12398-gc13320499ba0 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:hlock_class kernel/locking/lockdep.c:232 [inline] RIP: 0010:hlock_class+0xfa/0x130 kernel/locking/lockdep.c:221 Code: b6 14 11 38 d0 7c 04 84 d2 75 43 8b 05 33 33 77 0e 85 c0 75 19 90 48 c7 c6 00 bd 2c 8b 48 c7 c7 a0 b7 2c 8b e8 97 47 e5 ff 90 <0f> 0b 90 90 90 31 c0 eb 9e e8 f8 f8 7f 00 e9 1c ff ff ff 48 c7 c7 RSP: 0018:ffffc90003ee7918 EFLAGS: 00010082 RAX: 0000000000000000 RBX: 0000000000000ec4 RCX: ffffffff81510229 RDX: ffff88801e15c880 RSI: ffffffff81510236 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 000000002d2d2d2d R12: 0000000000000000 R13: 0000000000000000 R14: ffff88801e15d3b0 R15: 0000000000000ec4 FS: 0000000000000000(0000) GS:ffff88802c000000(0063) knlGS:0000000057702400 CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 000000005757f480 CR3: 0000000056d70000 CR4: 0000000000350ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> check_wait_context kernel/locking/lockdep.c:4773 [inline] __lock_acquire+0x3f2/0x3b30 kernel/locking/lockdep.c:5087 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719 touch_work_lockdep_map kernel/workqueue.c:3894 [inline] start_flush_work kernel/workqueue.c:4148 [inline] __flush_work+0x477/0xc60 kernel/workqueue.c:4181 xfs_inodegc_queue fs/xfs/xfs_icache.c:2119 [inline] xfs_inode_mark_reclaimable+0x6e8/0xf60 fs/xfs/xfs_icache.c:2149 destroy_inode+0xc4/0x1b0 fs/inode.c:311 iput_final fs/inode.c:1741 [inline] iput.part.0+0x5a8/0x7f0 fs/inode.c:1767 iput+0x5c/0x80 fs/inode.c:1757 do_unlinkat+0x613/0x750 fs/namei.c:4414 __do_sys_unlink fs/namei.c:4455 [inline] __se_sys_unlink fs/namei.c:4453 [inline] __ia32_sys_unlink+0xc6/0x110 fs/namei.c:4453 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline] __do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386 do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411 entry_SYSENTER_compat_after_hwframe+0x84/0x8e RIP: 0023:0xf725c579 Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 RSP: 002b:00000000ffb18bcc EFLAGS: 00000296 ORIG_RAX: 000000000000000a RAX: ffffffffffffffda RBX: 00000000ffb18c70 RCX: 0000000000008000 RDX: 00000000f73b2ff4 RSI: 0000000000000000 RDI: 00000000ffb19d10 RBP: 00000000ffb18c70 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> ---------------- Code disassembly (best guess), 2 bytes skipped: 0: 10 06 adc %al,(%rsi) 2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi 6: 10 07 adc %al,(%rdi) 8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi c: 10 08 adc %cl,(%rax) e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi 1e: 00 51 52 add %dl,0x52(%rcx) 21: 55 push %rbp 22: 89 e5 mov %esp,%ebp 24: 0f 34 sysenter 26: cd 80 int $0x80 * 28: 5d pop %rbp <-- trapping instruction 29: 5a pop %rdx 2a: 59 pop %rcx 2b: c3 ret 2c: 90 nop 2d: 90 nop 2e: 90 nop 2f: 90 nop 30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi 37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi --- 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