From: syzbot <syzbot+d222f4b7129379c3d5bc@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, linkinjeon@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mark@fasheh.com, mjguzik@gmail.com, ocfs2-devel@lists.linux.dev,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [exfat?] [ocfs2?] kernel BUG in link_path_walk
Date: Wed, 10 Dec 2025 03:19:02 -0800 [thread overview]
Message-ID: <69395726.a70a0220.33cd7b.0006.GAE@google.com> (raw)
In-Reply-To: <f2ui7rofuos4vcuj7t7pa5tcyq5m3agm44ouk7hcdl7opiwmwd@dyctf7rrsuqw>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in ocfs2_journal_toggle_dirty
(syz.0.554,7359,0):ocfs2_assign_bh:2417 ERROR: status = -30
(syz.0.554,7359,0):ocfs2_inode_lock_full_nested:2512 ERROR: status = -30
(syz.0.554,7359,0):ocfs2_shutdown_local_alloc:412 ERROR: status = -30
------------[ cut here ]------------
kernel BUG at fs/ocfs2/journal.c:1027!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 7359 Comm: syz.0.554 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_journal_toggle_dirty+0x33f/0x350 fs/ocfs2/journal.c:1027
Code: ff ff e8 44 bf b0 07 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 4e fe ff ff 48 89 df e8 fc 5a 7d fe e9 41 fe ff ff e8 f2 7e 15 fe 90 <0f> 0b 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90
RSP: 0018:ffffc9000d436fc0 EFLAGS: 00010293
RAX: ffffffff83ac415e RBX: 00000000ffffffff RCX: ffff88803ae90000
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: ffffc9000d437070 R08: ffffffff8fa21977 R09: 1ffffffff1f4432e
R10: dffffc0000000000 R11: fffffbfff1f4432f R12: 1ffff110024dca22
R13: ffff88804353b600 R14: ffff888011a24000 R15: ffff8880126e5110
FS: 00007ff6959f66c0(0000) GS:ffff88808d22f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3a33db2000 CR3: 000000005209e000 CR4: 0000000000352ef0
Call Trace:
<TASK>
ocfs2_journal_shutdown+0x524/0xab0 fs/ocfs2/journal.c:1109
ocfs2_mount_volume fs/ocfs2/super.c:1785 [inline]
ocfs2_fill_super+0x5574/0x63a0 fs/ocfs2/super.c:1083
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
vfs_get_tree+0x92/0x2a0 fs/super.c:1751
fc_mount fs/namespace.c:1199 [inline]
do_new_mount_fc fs/namespace.c:3636 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3712
do_mount fs/namespace.c:4035 [inline]
__do_sys_mount fs/namespace.c:4224 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4201
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff696390f6a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007ff6959f5e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ff6959f5ef0 RCX: 00007ff696390f6a
RDX: 0000200000004440 RSI: 0000200000000040 RDI: 00007ff6959f5eb0
RBP: 0000200000004440 R08: 00007ff6959f5ef0 R09: 00000000000008c0
R10: 00000000000008c0 R11: 0000000000000246 R12: 0000200000000040
R13: 00007ff6959f5eb0 R14: 0000000000004421 R15: 0000200000000080
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_journal_toggle_dirty+0x33f/0x350 fs/ocfs2/journal.c:1027
Code: ff ff e8 44 bf b0 07 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 4e fe ff ff 48 89 df e8 fc 5a 7d fe e9 41 fe ff ff e8 f2 7e 15 fe 90 <0f> 0b 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90
RSP: 0018:ffffc9000d436fc0 EFLAGS: 00010293
RAX: ffffffff83ac415e RBX: 00000000ffffffff RCX: ffff88803ae90000
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: ffffc9000d437070 R08: ffffffff8fa21977 R09: 1ffffffff1f4432e
R10: dffffc0000000000 R11: fffffbfff1f4432f R12: 1ffff110024dca22
R13: ffff88804353b600 R14: ffff888011a24000 R15: ffff8880126e5110
FS: 00007ff6959f66c0(0000) GS:ffff88808d22f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa8e1fff000 CR3: 000000005209e000 CR4: 0000000000352ef0
Tested on:
commit: 0048fbb4 Merge tag 'locking-futex-2025-12-10' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1477da1a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=de48dccdf203ea90
dashboard link: https://syzkaller.appspot.com/bug?extid=d222f4b7129379c3d5bc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=11e2ea1a580000
next prev parent reply other threads:[~2025-12-10 11:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 0:07 [syzbot] [exfat?] [ocfs2?] kernel BUG in link_path_walk syzbot
2025-12-04 0:46 ` Mateusz Guzik
2025-12-04 1:21 ` syzbot
2025-12-04 7:45 ` Mateusz Guzik
2025-12-04 8:21 ` Al Viro
2025-12-04 8:40 ` Mateusz Guzik
2025-12-10 9:45 ` [PATCH for 6.19-rc1] fs: preserve file type in make_bad_inode() unless invalid Tetsuo Handa
2025-12-10 10:09 ` Jan Kara
2025-12-10 10:24 ` Mateusz Guzik
2025-12-10 21:14 ` Al Viro
2025-12-10 23:27 ` Mateusz Guzik
2026-01-06 10:10 ` Tetsuo Handa
2026-01-07 9:36 ` Jan Kara
2026-01-07 9:53 ` Tetsuo Handa
2026-01-07 10:15 ` Jan Kara
2025-12-10 10:09 ` Mateusz Guzik
2025-12-10 15:35 ` Al Viro
2025-12-10 20:43 ` Al Viro
2025-12-10 20:55 ` Al Viro
2025-12-10 21:33 ` Al Viro
2025-12-04 9:09 ` [syzbot] [exfat?] [ocfs2?] kernel BUG in link_path_walk Mateusz Guzik
2025-12-04 10:13 ` syzbot
2025-12-04 10:15 ` Mateusz Guzik
2025-12-04 11:56 ` syzbot
2025-12-04 11:58 ` Mateusz Guzik
2025-12-10 11:00 ` Mateusz Guzik
2025-12-10 11:19 ` syzbot [this message]
2025-12-10 11:28 ` Mateusz Guzik
2025-12-10 19:44 ` Mateusz Guzik
2025-12-10 20:06 ` syzbot
2025-12-10 21:47 ` Al Viro
2025-12-10 22:09 ` syzbot
2025-12-11 9:00 ` Jan Kara
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=69395726.a70a0220.33cd7b.0006.GAE@google.com \
--to=syzbot+d222f4b7129379c3d5bc@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=mjguzik@gmail.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox