From: syzbot <syzbot+f8b081be889b639423bb@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_dio_wr_get_block
Date: Sun, 06 Apr 2025 18:06:24 -0700 [thread overview]
Message-ID: <67f32510.050a0220.0a13.0278.GAE@google.com> (raw)
In-Reply-To: <0000000000001e20c30621e8d767@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 0af2f6be1b42 Linux 6.15-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17abdb4c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=66996a2350ef05e0
dashboard link: https://syzkaller.appspot.com/bug?extid=f8b081be889b639423bb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14160c04580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d5923f980000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-0af2f6be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3fcfb8eefe4d/vmlinux-0af2f6be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e06a39be2bd8/bzImage-0af2f6be.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2b9582c348c6/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=1755923f980000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f8b081be889b639423bb@syzkaller.appspotmail.com
(syz-executor555,5473,0):__ocfs2_journal_access:705 ERROR: Error -30 getting 1 access to buffer!
(syz-executor555,5473,0):ocfs2_write_end_nolock:1942 ERROR: status = -30
(syz-executor555,5473,0):ocfs2_commit_trans:382 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/ocfs2/aops.c:2252!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5473 Comm: syz-executor555 Not tainted 6.15.0-rc1-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_dio_wr_get_block+0x18c1/0x18d0 fs/ocfs2/aops.c:2252
Code: 23 8f 4c 89 f2 e8 ff b9 7f 01 e9 38 f6 ff ff e8 45 6d 6f 08 e8 60 41 02 fe 90 0f 0b e8 58 41 02 fe 90 0f 0b e8 50 41 02 fe 90 <0f> 0b e8 48 41 02 fe 90 0f 0b 0f 1f 44 00 00 90 90 90 90 90 90 90
RSP: 0018:ffffc9000da3ece0 EFLAGS: 00010293
RAX: ffffffff83c113d0 RBX: 0000000000002000 RCX: ffff888000524880
RDX: 0000000000000000 RSI: 0000000000002000 RDI: 00000000ffffffe2
RBP: ffffc9000da3eed0 R08: ffffffff83c10e6d R09: 1ffffffff20bfbee
R10: dffffc0000000000 R11: fffffbfff20bfbef R12: 1ffff110023a150d
R13: dffffc0000000000 R14: 00000000ffffffe2 R15: ffff88804451cbd0
FS: 00007fb0138136c0(0000) GS:ffff88808c596000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb01389ad10 CR3: 0000000042406000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
get_more_blocks fs/direct-io.c:648 [inline]
do_direct_IO fs/direct-io.c:936 [inline]
__blockdev_direct_IO+0x1add/0x4540 fs/direct-io.c:1243
ocfs2_direct_IO+0x255/0x2c0 fs/ocfs2/aops.c:2438
generic_file_direct_write+0x1e8/0x400 mm/filemap.c:4036
__generic_file_write_iter+0x126/0x230 mm/filemap.c:4205
ocfs2_file_write_iter+0x190f/0x20d0 fs/ocfs2/file.c:2469
iter_file_splice_write+0xbdf/0x1530 fs/splice.c:738
do_splice_from fs/splice.c:935 [inline]
direct_splice_actor+0x11b/0x220 fs/splice.c:1158
splice_direct_to_actor+0x595/0xc90 fs/splice.c:1102
do_splice_direct_actor fs/splice.c:1201 [inline]
do_splice_direct+0x281/0x3d0 fs/splice.c:1227
do_sendfile+0x582/0x8c0 fs/read_write.c:1368
__do_sys_sendfile64 fs/read_write.c:1429 [inline]
__se_sys_sendfile64+0x17e/0x1e0 fs/read_write.c:1415
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb01385ee19
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 18 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb013813218 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fb0138ea6c8 RCX: 00007fb01385ee19
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000005
RBP: 00007fb0138ea6c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000080000013 R11: 0000000000000246 R12: 00007fb0138b7510
R13: 00002000000001c0 R14: 6f6f6c2f7665642f R15: 0000200000000140
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_dio_wr_get_block+0x18c1/0x18d0 fs/ocfs2/aops.c:2252
Code: 23 8f 4c 89 f2 e8 ff b9 7f 01 e9 38 f6 ff ff e8 45 6d 6f 08 e8 60 41 02 fe 90 0f 0b e8 58 41 02 fe 90 0f 0b e8 50 41 02 fe 90 <0f> 0b e8 48 41 02 fe 90 0f 0b 0f 1f 44 00 00 90 90 90 90 90 90 90
RSP: 0018:ffffc9000da3ece0 EFLAGS: 00010293
RAX: ffffffff83c113d0 RBX: 0000000000002000 RCX: ffff888000524880
RDX: 0000000000000000 RSI: 0000000000002000 RDI: 00000000ffffffe2
RBP: ffffc9000da3eed0 R08: ffffffff83c10e6d R09: 1ffffffff20bfbee
R10: dffffc0000000000 R11: fffffbfff20bfbef R12: 1ffff110023a150d
R13: dffffc0000000000 R14: 00000000ffffffe2 R15: ffff88804451cbd0
FS: 00007fb0138136c0(0000) GS:ffff88808c596000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005597594ba008 CR3: 0000000042406000 CR4: 0000000000352ef0
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.
prev parent reply other threads:[~2025-04-07 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 9:36 [syzbot] [ocfs2?] kernel BUG in ocfs2_dio_wr_get_block syzbot
2025-02-15 23:07 ` syzbot
2025-04-07 1:06 ` syzbot [this message]
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=67f32510.050a0220.0a13.0278.GAE@google.com \
--to=syzbot+f8b081be889b639423bb@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.