All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7c88f40b30ec95353951@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_write_begin_nolock
Date: Fri, 15 Nov 2024 22:37:37 -0800	[thread overview]
Message-ID: <67383db1.050a0220.85a0.000f.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    2d5404caa8c7 Linux 6.12-rc7
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=133a335f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1503500c6f615d24
dashboard link: https://syzkaller.appspot.com/bug?extid=7c88f40b30ec95353951
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: https://storage.googleapis.com/syzbot-assets/a2d329b82126/disk-2d5404ca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/37a04ca225dd/vmlinux-2d5404ca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4f837ce9d9dc/bzImage-2d5404ca.xz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/aops.c:1410!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 6836 Comm: syz.6.125 Not tainted 6.12.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:ocfs2_populate_write_desc fs/ocfs2/aops.c:1410 [inline]
RIP: 0010:ocfs2_write_begin_nolock+0x4da3/0x4ec0 fs/ocfs2/aops.c:1707
Code: e8 92 d7 11 fe 48 89 df e8 da 60 0f 00 e9 b5 fc ff ff e8 80 d7 11 fe e9 ab fc ff ff e8 76 d7 11 fe 90 0f 0b e8 6e d7 11 fe 90 <0f> 0b e8 66 d7 11 fe 90 0f 0b e8 5e d7 11 fe 90 0f 0b e8 56 d7 11
RSP: 0000:ffffc90004466f60 EFLAGS: 00010293
RAX: ffffffff83830242 RBX: 0000000000000002 RCX: ffff88801e743c00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffc90004467540 R08: ffffffff8382c05f R09: ffffffff8382c025
R10: 0000000000000006 R11: ffff88801e743c00 R12: 0000000000000000
R13: 1ffff1100ffea802 R14: 0000000000000000 R15: 0000000000000000
FS:  000055559101b500(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 0000000034ff8000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __ocfs2_page_mkwrite fs/ocfs2/mmap.c:93 [inline]
 ocfs2_page_mkwrite+0x752/0xed0 fs/ocfs2/mmap.c:144
 do_page_mkwrite+0x198/0x480 mm/memory.c:3162
 wp_page_shared mm/memory.c:3563 [inline]
 do_wp_page+0x23d3/0x52d0 mm/memory.c:3713
 handle_pte_fault+0x10e3/0x6820 mm/memory.c:5782
 __handle_mm_fault mm/memory.c:5909 [inline]
 handle_mm_fault+0x1053/0x1ad0 mm/memory.c:6077
 do_user_addr_fault arch/x86/mm/fault.c:1389 [inline]
 handle_page_fault arch/x86/mm/fault.c:1481 [inline]
 exc_page_fault+0x2b9/0x8c0 arch/x86/mm/fault.c:1539
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0033:0x7fb6b79461d8
Code: fc 89 37 c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 66 0f 1f 84 00 00 00 00 00 48 8b 4c 16 f8 48 8b 36 <48> 89 37 48 89 4c 17 f8 c3 c5 fe 6f 54 16 e0 c5 fe 6f 5c 16 c0 c5
RSP: 002b:00007ffc5c043b08 EFLAGS: 00010206
RAX: 0000000020000000 RBX: 0000000000000004 RCX: 006c7274635f6962
RDX: 000000000000000e RSI: 6962752f7665642f RDI: 0000000020000000
RBP: 00007fb6b7b37a80 R08: 00007fb6b7800000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000009 R12: 000000000001ceeb
R13: 00007ffc5c043c10 R14: 0000000000000032 R15: fffffffffffffffe
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_populate_write_desc fs/ocfs2/aops.c:1410 [inline]
RIP: 0010:ocfs2_write_begin_nolock+0x4da3/0x4ec0 fs/ocfs2/aops.c:1707
Code: e8 92 d7 11 fe 48 89 df e8 da 60 0f 00 e9 b5 fc ff ff e8 80 d7 11 fe e9 ab fc ff ff e8 76 d7 11 fe 90 0f 0b e8 6e d7 11 fe 90 <0f> 0b e8 66 d7 11 fe 90 0f 0b e8 5e d7 11 fe 90 0f 0b e8 56 d7 11
RSP: 0000:ffffc90004466f60 EFLAGS: 00010293
RAX: ffffffff83830242 RBX: 0000000000000002 RCX: ffff88801e743c00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffc90004467540 R08: ffffffff8382c05f R09: ffffffff8382c025
R10: 0000000000000006 R11: ffff88801e743c00 R12: 0000000000000000
R13: 1ffff1100ffea802 R14: 0000000000000000 R15: 0000000000000000
FS:  000055559101b500(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa88b6763b0 CR3: 0000000034ff8000 CR4: 00000000003526f0
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

                 reply	other threads:[~2024-11-16  6:37 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=67383db1.050a0220.85a0.000f.GAE@google.com \
    --to=syzbot+7c88f40b30ec95353951@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.