mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+42984127d45ad96219de@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_page_mkwrite (4)
Date: Sun, 24 May 2026 22:10:34 -0700	[thread overview]
Message-ID: <6a13d9ca.050a0220.7dd1.0000.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    df685633c3db Merge tag 'rcu-fixes.v7.1-20260519a' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14674c2e580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7f195f6be48c12ec
dashboard link: https://syzkaller.appspot.com/bug?extid=42984127d45ad96219de
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-df685633.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0d8ce459af2e/vmlinux-df685633.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5f8a4c255465/bzImage-df685633.xz

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

(syz.0.0,5323,0):__ocfs2_journal_access:724 ERROR: Error -30 getting 1 access to buffer!
(syz.0.0,5323,0):ocfs2_write_end_nolock:1945 ERROR: status = -30
(syz.0.0,5323,0):ocfs2_commit_trans:401 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/ocfs2/mmap.c:106!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5323 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__ocfs2_page_mkwrite fs/ocfs2/mmap.c:106 [inline]
RIP: 0010:ocfs2_page_mkwrite+0xb53/0xb60 fs/ocfs2/mmap.c:143
Code: 87 6a fe e9 bc fd ff ff e8 9a 0b e3 07 e8 d5 bb fd fd 4c 89 f7 48 c7 c6 e0 1c 13 8c e8 26 f6 5f fd 90 0f 0b e8 be bb fd fd 90 <0f> 0b cc cc cc cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc9000f937940 EFLAGS: 00010293
RAX: ffffffff83c81872 RBX: 00000000ffffffe2 RCX: ffff88801cf4a500
RDX: 0000000000000000 RSI: 0000000000001000 RDI: 00000000ffffffe2
RBP: ffffc9000f937ae0 R08: ffffffff9030f0f7 R09: 1ffffffff2061e1e
R10: dffffc0000000000 R11: fffffbfff2061e1f R12: 000000000000c000
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000001000
FS:  0000555567afd540(0000) GS:ffff88808c87e000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000020000000c000 CR3: 0000000041fff000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 do_page_mkwrite+0x14d/0x310 mm/memory.c:3684
 do_shared_fault mm/memory.c:5985 [inline]
 do_fault mm/memory.c:6047 [inline]
 do_pte_missing+0x6dc/0x33f0 mm/memory.c:4566
 handle_pte_fault mm/memory.c:6427 [inline]
 __handle_mm_fault mm/memory.c:6565 [inline]
 handle_mm_fault+0x1bd9/0x3170 mm/memory.c:6734
 do_user_addr_fault+0x75b/0x1340 arch/x86/mm/fault.c:1385
 handle_page_fault arch/x86/mm/fault.c:1474 [inline]
 exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1527
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618
RIP: 0033:0x7f762596d749
Code: dd 00 01 74 a3 83 f9 c0 0f 87 59 fe ff ff 62 e1 fe 28 6f 4e 01 48 29 fe 48 83 c7 3f 49 8d 0c 10 48 83 e7 c0 48 01 fe 48 29 f9 <f3> a4 62 c1 fe 28 7f 00 62 c1 fe 28 7f 48 01 c3 0f 1f 80 00 00 00
RSP: 002b:00007ffda9016b28 EFLAGS: 00010202
RAX: 00002000000079c0 RBX: 0000000000000004 RCX: 0000000000000ecb
RDX: 000000000000550b RSI: 00007f762540c53f RDI: 000020000000c000
RBP: fffffffffffffffe R08: 00002000000079c0 R09: 0000000000000002
R10: 000000000000550b R11: 0000000000000002 R12: 00007ffda9016c50
R13: 00007f7625c15fac R14: 0000000000014e7a R15: 00007f7625c15fa0
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__ocfs2_page_mkwrite fs/ocfs2/mmap.c:106 [inline]
RIP: 0010:ocfs2_page_mkwrite+0xb53/0xb60 fs/ocfs2/mmap.c:143
Code: 87 6a fe e9 bc fd ff ff e8 9a 0b e3 07 e8 d5 bb fd fd 4c 89 f7 48 c7 c6 e0 1c 13 8c e8 26 f6 5f fd 90 0f 0b e8 be bb fd fd 90 <0f> 0b cc cc cc cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc9000f937940 EFLAGS: 00010293
RAX: ffffffff83c81872 RBX: 00000000ffffffe2 RCX: ffff88801cf4a500
RDX: 0000000000000000 RSI: 0000000000001000 RDI: 00000000ffffffe2
RBP: ffffc9000f937ae0 R08: ffffffff9030f0f7 R09: 1ffffffff2061e1e
R10: dffffc0000000000 R11: fffffbfff2061e1f R12: 000000000000c000
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000001000
FS:  0000555567afd540(0000) GS:ffff88808c87e000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000020000000c000 CR3: 0000000041fff000 CR4: 0000000000352ef0


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

                 reply	other threads:[~2026-05-25  5:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6a13d9ca.050a0220.7dd1.0000.GAE@google.com \
    --to=syzbot+42984127d45ad96219de@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome