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: [syzbot] [ocfs2?] kernel BUG in ocfs2_dio_wr_get_block
Date: Thu, 12 Sep 2024 02:36:25 -0700 [thread overview]
Message-ID: <0000000000001e20c30621e8d767@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 8d8d276ba2fb Merge tag 'trace-v6.11-rc6' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=160d07c7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=61d235cb8d15001c
dashboard link: https://syzkaller.appspot.com/bug?extid=f8b081be889b639423bb
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-8d8d276b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d23708af23a4/vmlinux-8d8d276b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1aed2837c105/bzImage-8d8d276b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f8b081be889b639423bb@syzkaller.appspotmail.com
(syz.0.0,5118,0):__ocfs2_journal_access:705 ERROR: Error -30 getting 1 access to buffer!
(syz.0.0,5118,0):ocfs2_write_end_nolock:1967 ERROR: status = -30
(syz.0.0,5118,0):ocfs2_commit_trans:382 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/ocfs2/aops.c:2279!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5118 Comm: syz.0.0 Not tainted 6.11.0-rc7-syzkaller-00020-g8d8d276ba2fb #0
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+0x18bd/0x18d0 fs/ocfs2/aops.c:2279
Code: e1 8e 4c 89 f2 e8 23 f7 6b 01 e9 3a f6 ff ff e8 19 3d 39 08 e8 54 30 13 fe 90 0f 0b e8 4c 30 13 fe 90 0f 0b e8 44 30 13 fe 90 <0f> 0b e8 3c 30 13 fe 90 0f 0b 66 0f 1f 84 00 00 00 00 00 90 90 90
RSP: 0018:ffffc90002d6f060 EFLAGS: 00010287
RAX: ffffffff83805c6c RBX: 0000000000002000 RCX: 0000000000040000
RDX: ffffc9000b8c1000 RSI: 000000000001881d RDI: 000000000001881e
RBP: ffffc90002d6f250 R08: ffffffff8380570b R09: 1ffffffff283c928
R10: dffffc0000000000 R11: fffffbfff283c929 R12: 1ffff11006b8d50d
R13: dffffc0000000000 R14: 00000000ffffffe2 R15: ffff888040c68710
FS: 00007f1e355396c0(0000) GS:ffff88801fe00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000dc00000000 CR3: 000000003ca5a000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
get_more_blocks fs/direct-io.c:649 [inline]
do_direct_IO fs/direct-io.c:937 [inline]
__blockdev_direct_IO+0x1c90/0x4890 fs/direct-io.c:1249
ocfs2_direct_IO+0x257/0x2c0 fs/ocfs2/aops.c:2465
generic_file_direct_write+0x130/0x350 mm/filemap.c:3941
__generic_file_write_iter+0x129/0x230 mm/filemap.c:4107
ocfs2_file_write_iter+0x17b4/0x1f60 fs/ocfs2/file.c:2455
do_iter_readv_writev+0x60a/0x890
vfs_writev+0x37c/0xbb0 fs/read_write.c:971
do_pwritev fs/read_write.c:1072 [inline]
__do_sys_pwritev2 fs/read_write.c:1131 [inline]
__se_sys_pwritev2+0x1ca/0x2d0 fs/read_write.c:1122
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1e3477def9
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:00007f1e35539038 EFLAGS: 00000246 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007f1e34936058 RCX: 00007f1e3477def9
RDX: 0000000000000001 RSI: 0000000020000240 RDI: 0000000000000004
RBP: 00007f1e347f0b56 R08: 0000000000000030 R09: 0000000000000003
R10: 0000000000001400 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f1e34936058 R15: 00007ffd191ac778
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_dio_wr_get_block+0x18bd/0x18d0 fs/ocfs2/aops.c:2279
Code: e1 8e 4c 89 f2 e8 23 f7 6b 01 e9 3a f6 ff ff e8 19 3d 39 08 e8 54 30 13 fe 90 0f 0b e8 4c 30 13 fe 90 0f 0b e8 44 30 13 fe 90 <0f> 0b e8 3c 30 13 fe 90 0f 0b 66 0f 1f 84 00 00 00 00 00 90 90 90
RSP: 0018:ffffc90002d6f060 EFLAGS: 00010287
RAX: ffffffff83805c6c RBX: 0000000000002000 RCX: 0000000000040000
RDX: ffffc9000b8c1000 RSI: 000000000001881d RDI: 000000000001881e
RBP: ffffc90002d6f250 R08: ffffffff8380570b R09: 1ffffffff283c928
R10: dffffc0000000000 R11: fffffbfff283c929 R12: 1ffff11006b8d50d
R13: dffffc0000000000 R14: 00000000ffffffe2 R15: ffff888040c68710
FS: 00007f1e355396c0(0000) GS:ffff88801fe00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000dc00000000 CR3: 000000003ca5a000 CR4: 0000000000350ef0
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 syzkaller@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
next reply other threads:[~2024-09-12 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 9:36 syzbot [this message]
2025-02-15 23:07 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_dio_wr_get_block syzbot
2025-04-07 1:06 ` 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=0000000000001e20c30621e8d767@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.