| 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: <6854fb55.a00a0220.137b3.002f.GAE@google.com> Date: Thu, 19 Jun 2025 23:10:29 -0700 From: syzbot <syzbot+8882b2f5f48a7170a726@...kaller.appspotmail.com> To: jlbec@...lplan.org, joseph.qi@...ux.alibaba.com, linux-kernel@...r.kernel.org, mark@...heh.com, ocfs2-devel@...ts.linux.dev, syzkaller-bugs@...glegroups.com Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_remove_extent syzbot has found a reproducer for the following issue on: HEAD commit: 2c923c845768 Add linux-next specific files for 20250619 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=153d9d0c580000 kernel config: https://syzkaller.appspot.com/x/.config?x=58afc4b78b52b7e3 dashboard link: https://syzkaller.appspot.com/bug?extid=8882b2f5f48a7170a726 compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f23d0c580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/b4ef8488b2c5/disk-2c923c84.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/97fc575793ea/vmlinux-2c923c84.xz kernel image: https://storage.googleapis.com/syzbot-assets/b8095fa1838d/bzImage-2c923c84.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/3778419fa82a/mount_0.gz fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=1441f5d4580000) IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+8882b2f5f48a7170a726@...kaller.appspotmail.com ------------[ cut here ]------------ kernel BUG at fs/ocfs2/alloc.c:5581! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 6023 Comm: syz.1.19 Not tainted 6.16.0-rc2-next-20250619-syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 RIP: 0010:ocfs2_remove_extent+0x1ecf/0x2020 fs/ocfs2/alloc.c:5581 Code: fa ff ff 48 8b 4c 24 08 80 e1 07 fe c1 38 c1 0f 8c 95 fa ff ff 48 8b 7c 24 08 e8 7c 70 8e fe e9 86 fa ff ff e8 d2 49 2a fe 90 <0f> 0b f3 0f 1e fa 44 89 6c 24 10 65 8b 1d 63 61 09 0f bf 07 00 00 RSP: 0000:ffffc9000216e640 EFLAGS: 00010293 RAX: ffffffff83961ebe RBX: ffffc9000216ee38 RCX: ffff888034273c00 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000006 RBP: ffffc9000216e990 R08: ffff888034273c00 R09: 0000000000000006 R10: 00000000fffffffc R11: 0000000000000000 R12: 1ffff1100b8fb49a R13: 0000000000000006 R14: ffff88805c7da4d0 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff888125d28000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fff5456df38 CR3: 0000000075e08000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ocfs2_remove_btree_range+0xdef/0x1540 fs/ocfs2/alloc.c:5778 ocfs2_commit_truncate+0xb64/0x21d0 fs/ocfs2/alloc.c:7373 ocfs2_truncate_for_delete fs/ocfs2/inode.c:637 [inline] ocfs2_wipe_inode fs/ocfs2/inode.c:804 [inline] ocfs2_delete_inode fs/ocfs2/inode.c:1093 [inline] ocfs2_evict_inode+0x1138/0x40e0 fs/ocfs2/inode.c:1230 evict+0x501/0x9c0 fs/inode.c:810 ocfs2_dentry_iput+0x247/0x370 fs/ocfs2/dcache.c:407 __dentry_kill+0x209/0x660 fs/dcache.c:669 dput+0x19f/0x2b0 fs/dcache.c:911 __fput+0x68e/0xa70 fs/file_table.c:476 task_work_run+0x1d1/0x260 kernel/task_work.c:227 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0x6b5/0x2300 kernel/exit.c:959 do_group_exit+0x21c/0x2d0 kernel/exit.c:1100 get_signal+0x1286/0x1340 kernel/signal.c:3034 arch_do_signal_or_restart+0x9a/0x750 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline] irqentry_exit_to_user_mode+0x81/0x120 kernel/entry/common.c:184 exc_page_fault+0x9f/0xf0 arch/x86/mm/fault.c:1535 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0033:0x7f056b38e886 Code: Unable to access opcode bytes at 0x7f056b38e85c. RSP: 002b:00007ffea35be310 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000058 RCX: 00007f056b38e929 RDX: 00007ffea35be350 RSI: 0000000000000000 RDI: 00000000000249f0 RBP: 00007f056b410b39 R08: 0000000000000000 R09: 0000000000000058 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f056b5b5fa0 R14: 00007f056b5b5fa0 R15: 0000000000000002 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:ocfs2_remove_extent+0x1ecf/0x2020 fs/ocfs2/alloc.c:5581 Code: fa ff ff 48 8b 4c 24 08 80 e1 07 fe c1 38 c1 0f 8c 95 fa ff ff 48 8b 7c 24 08 e8 7c 70 8e fe e9 86 fa ff ff e8 d2 49 2a fe 90 <0f> 0b f3 0f 1e fa 44 89 6c 24 10 65 8b 1d 63 61 09 0f bf 07 00 00 RSP: 0000:ffffc9000216e640 EFLAGS: 00010293 RAX: ffffffff83961ebe RBX: ffffc9000216ee38 RCX: ffff888034273c00 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000006 RBP: ffffc9000216e990 R08: ffff888034273c00 R09: 0000000000000006 R10: 00000000fffffffc R11: 0000000000000000 R12: 1ffff1100b8fb49a R13: 0000000000000006 R14: ffff88805c7da4d0 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff888125d28000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7a6d9f37b0 CR3: 00000000338ec000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 --- If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing.
Powered by blists - more mailing lists