public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+18a87160c7d64ba2e2f6@syzkaller.appspotmail.com>
To: heming.zhao@suse.com, joseph.qi@linux.alibaba.com,
	 linux-kernel@vger.kernel.org, ocfs2-devel@lists.linux.dev,
	 pvmohammedanees2003@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_write_cluster_by_desc
Date: Mon, 23 Sep 2024 01:31:02 -0700	[thread overview]
Message-ID: <66f12746.050a0220.c23dd.000c.GAE@google.com> (raw)
In-Reply-To: <0a4b798a-db82-40da-9167-141b684f43fa@suse.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in ocfs2_write_cluster_by_desc

loop0: detected capacity change from 0 to 32768
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/aops.c:1179!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5600 Comm: syz.0.16 Not tainted 6.11.0-syzkaller-08833-gde5cb0dcb74c-dirty #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_write_cluster fs/ocfs2/aops.c:1179 [inline]
RIP: 0010:ocfs2_write_cluster_by_desc+0x207b/0x20b0 fs/ocfs2/aops.c:1240
Code: 03 48 8d bc 24 30 02 00 00 48 c7 c6 2e 2b 11 8e ba 7e 04 00 00 48 c7 c1 80 23 49 8c e8 7e 96 1d 00 90 0f 0b e8 c6 b7 0f fe 90 <0f> 0b e8 be b7 0f fe 90 0f 0b e8 b6 b7 0f fe 90 0f 0b e8 ae b7 0f
RSP: 0018:ffffc90002a3ee20 EFLAGS: 00010293
RAX: ffffffff838501ea RBX: ffff8880493116e0 RCX: ffff88801fa3c880
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90002a3f170 R08: ffffffff8384e89e R09: 1ffff110092622ac
R10: dffffc0000000000 R11: ffffed10092622ad R12: 0000000000000000
R13: ffff8880126f0000 R14: ffff8880493116b8 R15: 0000000000000000
FS:  00007f40e6b146c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020201000 CR3: 000000001317a000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ocfs2_write_begin_nolock+0x3a2f/0x4ec0 fs/ocfs2/aops.c:1816
 ocfs2_write_begin+0x205/0x3a0 fs/ocfs2/aops.c:1903
 generic_perform_write+0x344/0x6d0 mm/filemap.c:4050
 ocfs2_file_write_iter+0x17b1/0x1f50 fs/ocfs2/file.c:2456
 new_sync_write fs/read_write.c:590 [inline]
 vfs_write+0xa6d/0xc90 fs/read_write.c:683
 ksys_write+0x1a0/0x2c0 fs/read_write.c:736
 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:0x7f40e5d7def9
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:00007f40e6b14038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f40e5f35f80 RCX: 00007f40e5d7def9
RDX: 000000000208e24b RSI: 0000000020000240 RDI: 0000000000000004
RBP: 00007f40e5df0b76 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f40e5f35f80 R15: 00007ffed859a9e8
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_write_cluster fs/ocfs2/aops.c:1179 [inline]
RIP: 0010:ocfs2_write_cluster_by_desc+0x207b/0x20b0 fs/ocfs2/aops.c:1240
Code: 03 48 8d bc 24 30 02 00 00 48 c7 c6 2e 2b 11 8e ba 7e 04 00 00 48 c7 c1 80 23 49 8c e8 7e 96 1d 00 90 0f 0b e8 c6 b7 0f fe 90 <0f> 0b e8 be b7 0f fe 90 0f 0b e8 b6 b7 0f fe 90 0f 0b e8 ae b7 0f
RSP: 0018:ffffc90002a3ee20 EFLAGS: 00010293
RAX: ffffffff838501ea RBX: ffff8880493116e0 RCX: ffff88801fa3c880
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90002a3f170 R08: ffffffff8384e89e R09: 1ffff110092622ac
R10: dffffc0000000000 R11: ffffed10092622ad R12: 0000000000000000
R13: ffff8880126f0000 R14: ffff8880493116b8 R15: 0000000000000000
FS:  00007f40e6b146c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020201000 CR3: 000000001317a000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


Tested on:

commit:         de5cb0dc Merge branch 'address-masking'
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b99c27980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5b5c53071a819d59
dashboard link: https://syzkaller.appspot.com/bug?extid=18a87160c7d64ba2e2f6
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=148fc107980000


  reply	other threads:[~2024-09-23  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 18:35 [syzbot] [ocfs2?] kernel BUG in ocfs2_write_cluster_by_desc syzbot
2024-09-17 16:26 ` [syzbot] " syzbot
2024-09-18 15:22 ` syzbot
2024-09-18 15:53 ` syzbot
2024-09-23  8:15 ` [syzbot] [ocfs2?] " heming.zhao
2024-09-23  8:31   ` syzbot [this message]
     [not found] <CAABpPxQfOeRrSwxu3NZCVRQUcEguEqabK6DJ9GPFJ2twY+EdPw@mail.gmail.com>
2024-09-17 16:41 ` syzbot
     [not found] <CAABpPxQ3+-wyEeGsVc+9ihNxDGFUFVQSWHKHSJnVQH6jSfYoRQ@mail.gmail.com>
2024-09-18 15:38 ` syzbot
     [not found] <CAABpPxTDRvwd_Z4TV7-iba9t1xjWqg3HU+vfZ-XEa0O2ALpqaQ@mail.gmail.com>
2024-09-18 16:14 ` 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=66f12746.050a0220.c23dd.000c.GAE@google.com \
    --to=syzbot+18a87160c7d64ba2e2f6@syzkaller.appspotmail.com \
    --cc=heming.zhao@suse.com \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=pvmohammedanees2003@gmail.com \
    --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