Hello,
syzbot found the following issue on:
HEAD commit: 74cdd62cb470 Linux 5.15.169
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=146614f7980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=5a9622b27b0be51a
dashboard link:
https://syzkaller.appspot.com/bug?extid=f526a0c9abb316ed23be
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/100cab3ab8cf/disk-74cdd62c.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/8eab59bf613d/vmlinux-74cdd62c.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/e815c18aac36/bzImage-74cdd62c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f526a0...@syzkaller.appspotmail.com
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:1387!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8956 Comm: syz.1.956 Not tainted 5.15.169-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:ocfs2_find_victim_chain fs/ocfs2/suballoc.c:1387 [inline]
RIP: 0010:ocfs2_claim_suballoc_bits+0x2355/0x24b0 fs/ocfs2/suballoc.c:1927
Code: 86 fa ff ff e8 5c 4a 3e fe 0f 0b e8 55 4a 3e fe 0f 0b e8 4e 4a 3e fe 0f 0b e8 47 4a 3e fe 0f 0b e8 30 d5 f1 06 e8 3b 4a 3e fe <0f> 0b e8 34 4a 3e fe 0f 0b 65 8b 1d a3 eb bf 7c bf 07 00 00 00 89
RSP: 0018:ffffc90002eb7260 EFLAGS: 00010287
RAX: ffffffff834229a5 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000394b000 RSI: 0000000000001fba RDI: 0000000000001fbb
RBP: ffffc90002eb7510 R08: ffffffff83421423 R09: ffffc90002eb75a0
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88806226f088 R14: dffffc0000000000 R15: 0000000000000002
FS: 00007fb1baf5f6c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdd8a0030f0 CR3: 0000000074a6c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_claim_new_inode+0x32b/0x850 fs/ocfs2/suballoc.c:2210
ocfs2_mknod_locked+0x176/0x3a0 fs/ocfs2/namei.c:633
ocfs2_mknod+0x187f/0x2cd0 fs/ocfs2/namei.c:379
ocfs2_mkdir+0x194/0x430 fs/ocfs2/namei.c:655
vfs_mkdir+0x3b6/0x590 fs/namei.c:4065
do_mkdirat+0x260/0x520 fs/namei.c:4090
__do_sys_mkdirat fs/namei.c:4105 [inline]
__se_sys_mkdirat fs/namei.c:4103 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4103
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fb1bcae7719
Code: ff ff 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb1baf5f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fb1bcc9ef80 RCX: 00007fb1bcae7719
RDX: 0000000000000000 RSI: 0000000020002040 RDI: ffffffffffffff9c
RBP: 00007fb1bcb5a32e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fb1bcc9ef80 R15: 00007ffe2a8cac48
</TASK>
Modules linked in:
---[ end trace 74bdb722dff06db7 ]---
RIP: 0010:ocfs2_find_victim_chain fs/ocfs2/suballoc.c:1387 [inline]
RIP: 0010:ocfs2_claim_suballoc_bits+0x2355/0x24b0 fs/ocfs2/suballoc.c:1927
Code: 86 fa ff ff e8 5c 4a 3e fe 0f 0b e8 55 4a 3e fe 0f 0b e8 4e 4a 3e fe 0f 0b e8 47 4a 3e fe 0f 0b e8 30 d5 f1 06 e8 3b 4a 3e fe <0f> 0b e8 34 4a 3e fe 0f 0b 65 8b 1d a3 eb bf 7c bf 07 00 00 00 89
RSP: 0018:ffffc90002eb7260 EFLAGS: 00010287
RAX: ffffffff834229a5 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000394b000 RSI: 0000000000001fba RDI: 0000000000001fbb
RBP: ffffc90002eb7510 R08: ffffffff83421423 R09: ffffc90002eb75a0
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88806226f088 R14: dffffc0000000000 R15: 0000000000000002
FS: 00007fb1baf5f6c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000074a6c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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
syzk...@googlegroups.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