[v5.15] kernel BUG in _ocfs2_free_suballoc_bits

5 views
Skip to first unread message

syzbot

unread,
Nov 29, 2024, 2:55:31 PM11/29/24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 0a51d2d4527b Linux 5.15.173
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=160e6f78580000
kernel config: https://syzkaller.appspot.com/x/.config?x=69147a3052c29ea2
dashboard link: https://syzkaller.appspot.com/bug?extid=ecd45d8ac70d5d0045a7
compiler: Debian clang version 15.0.6, 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: https://storage.googleapis.com/syzbot-assets/cbeb11c653b7/disk-0a51d2d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b646052737b/vmlinux-0a51d2d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0f7e7bafd5b2/Image-0a51d2d4.gz.xz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:2484!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4021 Comm: syz-executor Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : _ocfs2_free_suballoc_bits+0xe4c/0x10cc fs/ocfs2/suballoc.c:2484
lr : _ocfs2_free_suballoc_bits+0xe4c/0x10cc fs/ocfs2/suballoc.c:2484
sp : ffff80001fd87040
x29: ffff80001fd871a0 x28: ffff700003fb0e18 x27: ffff0000e90953a0
x26: 0000000000000001 x25: 0000000000000000 x24: dfff800000000000
x23: 0000000000000002 x22: 0000000000000001 x21: 0000000000000000
x20: ffff0000ec07400a x19: ffff0000f3c08000 x18: ffff80001fd86a40
x17: 0000000000000000 x16: ffff800011b4c108 x15: 0000000000037215
x14: 1ffff0000296c06c x13: dfff800000000000 x12: ffff80001fd86f40
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c5f351c0
x8 : ffff800009f0c104 x7 : ffff800009e8bde8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0000e90953a0 x1 : 0000000000000000 x0 : 0000000000000002
Call trace:
_ocfs2_free_suballoc_bits+0xe4c/0x10cc fs/ocfs2/suballoc.c:2484
ocfs2_free_suballoc_bits fs/ocfs2/suballoc.c:2521 [inline]
ocfs2_free_dinode+0xb0/0xe8 fs/ocfs2/suballoc.c:2536
ocfs2_remove_inode fs/ocfs2/inode.c:696 [inline]
ocfs2_wipe_inode fs/ocfs2/inode.c:818 [inline]
ocfs2_delete_inode fs/ocfs2/inode.c:1079 [inline]
ocfs2_evict_inode+0x2620/0x45ec fs/ocfs2/inode.c:1216
evict+0x418/0x894 fs/inode.c:622
iput_final fs/inode.c:1744 [inline]
iput+0x744/0x824 fs/inode.c:1770
d_delete_notify include/linux/fsnotify.h:267 [inline]
vfs_rmdir+0x2f8/0x3f0 fs/namei.c:4162
do_rmdir+0x2e8/0x84c fs/namei.c:4210
__do_sys_unlinkat fs/namei.c:4390 [inline]
__se_sys_unlinkat fs/namei.c:4384 [inline]
__arm64_sys_unlinkat+0xe0/0xfc fs/namei.c:4384
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 9796e082 f94013fc 17fffcd2 9796e07f (d4210000)
---[ end trace cb6158e1ab027d23 ]---


---
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

syzbot

unread,
Nov 29, 2024, 4:19:26 PM11/29/24
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 0a51d2d4527b Linux 5.15.173
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11b2bf5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=69147a3052c29ea2
dashboard link: https://syzkaller.appspot.com/bug?extid=ecd45d8ac70d5d0045a7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16fbf3c0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ee19e8580000
mounted in repro: https://storage.googleapis.com/syzbot-assets/a0f816947a07/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:2484!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4026 Comm: syz-executor179 Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : _ocfs2_free_suballoc_bits+0xe4c/0x10cc fs/ocfs2/suballoc.c:2484
lr : _ocfs2_free_suballoc_bits+0xe4c/0x10cc fs/ocfs2/suballoc.c:2484
sp : ffff80001fe47040
x29: ffff80001fe471a0 x28: ffff700003fc8e18 x27: ffff0000e2455000
x26: 0000000000000001 x25: 0000000000000000 x24: dfff800000000000
x23: 0000000000000002 x22: 0000000000000001 x21: 0000000000000000
x20: ffff0000e33e300a x19: ffff0000e2490000 x18: ffff80001fe46740
x17: 1fffe0003683318e x16: ffff800011b4c108 x15: 000000000000c46a
x14: 1ffff0000296c06c x13: dfff800000000000 x12: ffff80001fe46f40
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000dac11b40
x8 : ffff800009f0c104 x7 : ffff800009e8bde8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0000e2455000 x1 : 0000000000000000 x0 : 0000000000000002
---[ end trace 0ad4f5d0be2410f3 ]---


---
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.
Reply all
Reply to author
Forward
0 new messages