From: syzbot <syzbot+8882b2f5f48a7170a726@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_remove_extent
Date: Thu, 28 Aug 2025 18:50:33 -0700 [thread overview]
Message-ID: <68b10769.050a0220.3db4df.00f3.GAE@google.com> (raw)
In-Reply-To: <683bef14.a70a0220.1a6ae.0011.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 07d9df80082b Merge tag 'perf-tools-fixes-for-v6.17-2025-08..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17bdfc42580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a7016efe6aaa498c
dashboard link: https://syzkaller.appspot.com/bug?extid=8882b2f5f48a7170a726
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115a4262580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13087ef0580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-07d9df80.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/64a01edfb5ff/vmlinux-07d9df80.xz
kernel image: https://storage.googleapis.com/syzbot-assets/78c915400ff9/bzImage-07d9df80.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/7dc3c9b29fa5/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=165a4262580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8882b2f5f48a7170a726@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/ocfs2/alloc.c:5581!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5722 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
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 4c 35 8d fe e9 86 fa ff ff e8 f2 48 28 fe 90 <0f> 0b f3 0f 1e fa 44 89 6c 24 10 65 8b 1d d3 9d 09 0f bf 07 00 00
RSP: 0018:ffffc9000d56e640 EFLAGS: 00010293
RAX: ffffffff8397724e RBX: ffffc9000d56ee38 RCX: ffff88803eab8000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000007
RBP: ffffc9000d56e990 R08: ffff88803eab8000 R09: 0000000000000006
R10: 00000000fffffffc R11: 0000000000000000 R12: 1ffff11008b38e9a
R13: 0000000000000007 R14: ffff8880459c74d0 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff88808d20f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2cce600218 CR3: 000000004b419000 CR4: 0000000000352ef0
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:699 [inline]
ocfs2_wipe_inode fs/ocfs2/inode.c:866 [inline]
ocfs2_delete_inode fs/ocfs2/inode.c:1155 [inline]
ocfs2_evict_inode+0x1138/0x40e0 fs/ocfs2/inode.c:1292
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+0x1d4/0x260 kernel/task_work.c:227
exit_task_work include/linux/task_work.h:40 [inline]
do_exit+0x6b5/0x2300 kernel/exit.c:961
do_group_exit+0x21c/0x2d0 kernel/exit.c:1102
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:40 [inline]
exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
irqentry_exit_to_user_mode+0x81/0x120 kernel/entry/common.c:73
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:0x7f018c18ebf1
Code: Unable to access opcode bytes at 0x7f018c18ebc7.
RSP: 002b:00000000fffffeb0 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f018c3b5fa0 RCX: 00007f018c18ebe9
RDX: 0000000000000000 RSI: 00000000fffffeb0 RDI: 0000000002000400
RBP: 00007f018c211e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 00007f018c3b6038 R14: 00007f018c3b5fa0 R15: 00007ffc298dcef8
</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 4c 35 8d fe e9 86 fa ff ff e8 f2 48 28 fe 90 <0f> 0b f3 0f 1e fa 44 89 6c 24 10 65 8b 1d d3 9d 09 0f bf 07 00 00
RSP: 0018:ffffc9000d56e640 EFLAGS: 00010293
RAX: ffffffff8397724e RBX: ffffc9000d56ee38 RCX: ffff88803eab8000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000007
RBP: ffffc9000d56e990 R08: ffff88803eab8000 R09: 0000000000000006
R10: 00000000fffffffc R11: 0000000000000000 R12: 1ffff11008b38e9a
R13: 0000000000000007 R14: ffff8880459c74d0 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff88808d20f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f67141f3000 CR3: 00000000333eb000 CR4: 0000000000352ef0
---
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.
next prev parent reply other threads:[~2025-08-29 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 6:11 [syzbot] [ocfs2?] kernel BUG in ocfs2_remove_extent syzbot
2025-06-20 6:10 ` syzbot
2025-08-29 1:50 ` syzbot [this message]
2025-10-22 15:04 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 552c50713f273b494ac6c77052032a49bc9255e2 syzbot
2026-01-07 5:41 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_remove_extent syzbot
[not found] <20251022150444.jHFNw%dmantipov@yandex.ru>
2025-10-22 15:21 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68b10769.050a0220.3db4df.00f3.GAE@google.com \
--to=syzbot+8882b2f5f48a7170a726@syzkaller.appspotmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.