All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+901524eae72170197041@syzkaller.appspotmail.com>
To: agruenba@redhat.com, anprice@redhat.com, gfs2@lists.linux.dev,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] kernel BUG in gfs2_withdraw (2)
Date: Mon, 25 Aug 2025 22:27:31 -0700	[thread overview]
Message-ID: <68ad45c3.050a0220.37038e.00a6.GAE@google.com> (raw)
In-Reply-To: <68a2184c.050a0220.e29e5.0070.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    b6add54ba618 Merge tag 'pinctrl-v6.17-2' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=174cf862580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a7016efe6aaa498c
dashboard link: https://syzkaller.appspot.com/bug?extid=901524eae72170197041
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12dc8634580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16dc8634580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-b6add54b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a6e94bac86a3/vmlinux-b6add54b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0c9cbb4d239d/bzImage-b6add54b.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/df6a4ddf7d5b/mount_0.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=13dcc462580000)

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

gfs2: fsid=syz:syz.s: fatal: invalid metadata block - bh = 19 (type: exp=4, found=1), function = gfs2_meta_buffer, file = fs/gfs2/meta_io.c, line = 499
gfs2: fsid=syz:syz.s: about to withdraw this file system
------------[ cut here ]------------
kernel BUG at fs/gfs2/util.c:331!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5528 Comm: syz.0.17 Not tainted 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:gfs2_withdraw+0x137b/0x1430 fs/gfs2/util.c:331
Code: ff ff 48 8b 4c 24 18 80 e1 07 80 c1 03 38 c1 0f 8c 55 fb ff ff 48 8b 7c 24 18 e8 90 56 25 fe e9 46 fb ff ff e8 06 6a c0 fd 90 <0f> 0b 48 8b 4c 24 18 80 e1 07 80 c1 03 38 c1 0f 8c ab fb ff ff 48
RSP: 0018:ffffc90002bff2a0 EFLAGS: 00010293
RAX: ffffffff83ff513a RBX: ffffc90002bff360 RCX: ffff8880003f2440
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
RBP: ffffc90002bff430 R08: ffff88801fc24253 R09: 1ffff11003f8484a
R10: dffffc0000000000 R11: ffffed1003f8484b R12: dffffc0000000000
R13: 1ffff9200057fe68 R14: 1ffff110066ba015 R15: 0000000000000004
FS:  0000555589e6b500(0000) GS:ffff88808d210000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa802461000 CR3: 00000000346f0000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 gfs2_metatype_check_ii+0x78/0x90 fs/gfs2/util.c:514
 gfs2_metatype_check_i fs/gfs2/util.h:129 [inline]
 gfs2_meta_buffer+0x25e/0x300 fs/gfs2/meta_io.c:499
 gfs2_meta_inode_buffer fs/gfs2/meta_io.h:70 [inline]
 gfs2_inode_refresh fs/gfs2/glops.c:484 [inline]
 inode_go_instantiate+0xdf/0x1260 fs/gfs2/glops.c:509
 gfs2_instantiate+0x165/0x220 fs/gfs2/glock.c:468
 gfs2_glock_holder_ready fs/gfs2/glock.c:1332 [inline]
 gfs2_glock_wait+0x1d4/0x2a0 fs/gfs2/glock.c:1352
 gfs2_glock_nq_init fs/gfs2/glock.h:248 [inline]
 check_journal_clean+0x11c/0x310 fs/gfs2/util.c:61
 init_journal+0x17f8/0x2260 fs/gfs2/ops_fstype.c:793
 init_inodes+0xdb/0x320 fs/gfs2/ops_fstype.c:851
 gfs2_fill_super+0x1923/0x20d0 fs/gfs2/ops_fstype.c:1253
 get_tree_bdev_flags+0x40b/0x4d0 fs/super.c:1692
 gfs2_get_tree+0x51/0x1e0 fs/gfs2/ops_fstype.c:1335
 vfs_get_tree+0x92/0x2b0 fs/super.c:1815
 do_new_mount+0x2a2/0x9e0 fs/namespace.c:3808
 do_mount fs/namespace.c:4136 [inline]
 __do_sys_mount fs/namespace.c:4347 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4324
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbbb439038a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007ffccc5a4b98 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffccc5a4c20 RCX: 00007fbbb439038a
RDX: 0000200000000400 RSI: 0000200000012500 RDI: 00007ffccc5a4be0
RBP: 0000200000000400 R08: 00007ffccc5a4c20 R09: 0000000000200000
R10: 0000000000200000 R11: 0000000000000246 R12: 0000200000012500
R13: 00007ffccc5a4be0 R14: 00000000000125bb R15: 0000200000000f40
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:gfs2_withdraw+0x137b/0x1430 fs/gfs2/util.c:331
Code: ff ff 48 8b 4c 24 18 80 e1 07 80 c1 03 38 c1 0f 8c 55 fb ff ff 48 8b 7c 24 18 e8 90 56 25 fe e9 46 fb ff ff e8 06 6a c0 fd 90 <0f> 0b 48 8b 4c 24 18 80 e1 07 80 c1 03 38 c1 0f 8c ab fb ff ff 48
RSP: 0018:ffffc90002bff2a0 EFLAGS: 00010293
RAX: ffffffff83ff513a RBX: ffffc90002bff360 RCX: ffff8880003f2440
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
RBP: ffffc90002bff430 R08: ffff88801fc24253 R09: 1ffff11003f8484a
R10: dffffc0000000000 R11: ffffed1003f8484b R12: dffffc0000000000
R13: 1ffff9200057fe68 R14: 1ffff110066ba015 R15: 0000000000000004
FS:  0000555589e6b500(0000) GS:ffff88808d210000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc5ba20d000 CR3: 00000000346f0000 CR4: 0000000000352ef0


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

      parent reply	other threads:[~2025-08-26  5:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 17:58 [syzbot] [gfs2?] kernel BUG in gfs2_withdraw (2) syzbot
2025-08-18 12:43 ` Andrew Price
2025-08-26  5:27 ` 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=68ad45c3.050a0220.37038e.00a6.GAE@google.com \
    --to=syzbot+901524eae72170197041@syzkaller.appspotmail.com \
    --cc=agruenba@redhat.com \
    --cc=anprice@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --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.