All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ef4ad020dc976d178975@syzkaller.appspotmail.com>
To: agruenba@redhat.com, gfs2@lists.linux.dev,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] kernel BUG in __gfs2_glock_put (2)
Date: Tue, 04 Nov 2025 21:01:23 -0800	[thread overview]
Message-ID: <690ada23.050a0220.baf87.0008.GAE@google.com> (raw)
In-Reply-To: <68550350.a00a0220.137b3.0032.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    c9cfc122f037 Merge tag 'for-6.18-rc4-tag' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1721a17c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=929790bc044e87d7
dashboard link: https://syzkaller.appspot.com/bug?extid=ef4ad020dc976d178975
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11c42084580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11df2114580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-c9cfc122.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c3f2cad59d49/vmlinux-c9cfc122.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a4cfb61ba836/bzImage-c9cfc122.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3d8068067f45/mount_0.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=104bc012580000)

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

loop0: rw=12288, sector=18446744073709551608, nr_sectors = 8 limit=32768
gfs2: fsid=syz:syz.s: Error -5 locking journal for spectator mount.
gfs2: fsid=syz:syz.s: G:  s:UN n:2/ffffffffffffffff f:an t:UN d:EX/0 a:0 v:0 r:-128 m:20 p:1
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:274!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5494 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_glock_put+0x384/0x3e0 fs/gfs2/glock.c:274
Code: 3f 48 89 de e8 7d 0f ff ff eb 26 e8 b6 38 c3 fd e9 30 fe ff ff e8 ac 38 c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 2d df ff ff 90 <0f> 0b e8 95 38 c3 fd 31 f6 65 ff 0d 8c 02 72 0e 40 0f 94 c5 40 0f
RSP: 0018:ffffc90002a6f408 EFLAGS: 00010246
RAX: 29c52adf4a6b3d00 RBX: ffff88801131cfd8 RCX: ffff8880002c0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffc90002a6ecc7 R09: 1ffff9200054dd98
R10: dffffc0000000000 R11: fffff5200054dd99 R12: dffffc0000000000
R13: 1ffff11007cab015 R14: ffff88803e558000 R15: ffff88801131d2c8
FS:  0000555578b1a500(0000) GS:ffff88808d732000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f461a63048 CR3: 00000000126a6000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 gfs2_glock_put_eventually fs/gfs2/super.c:1183 [inline]
 gfs2_evict_inode+0xae7/0x1000 fs/gfs2/super.c:1458
 evict+0x504/0x9c0 fs/inode.c:810
 gfs2_jindex_free+0x39c/0x440 fs/gfs2/super.c:79
 init_journal+0x8f1/0x2260 fs/gfs2/ops_fstype.c:833
 init_inodes+0xdb/0x320 fs/gfs2/ops_fstype.c:851
 gfs2_fill_super+0x1923/0x20d0 fs/gfs2/ops_fstype.c:1255
 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
 gfs2_get_tree+0x51/0x1e0 fs/gfs2/ops_fstype.c:1337
 vfs_get_tree+0x92/0x2b0 fs/super.c:1751
 fc_mount fs/namespace.c:1208 [inline]
 do_new_mount_fc fs/namespace.c:3651 [inline]
 do_new_mount+0x302/0xa10 fs/namespace.c:3727
 do_mount fs/namespace.c:4050 [inline]
 __do_sys_mount fs/namespace.c:4238 [inline]
 __se_sys_mount+0x313/0x410 fs/namespace.c:4215
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9033190e6a
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:00007ffc08e3a548 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffc08e3a5d0 RCX: 00007f9033190e6a
RDX: 0000200000000400 RSI: 0000200000012500 RDI: 00007ffc08e3a590
RBP: 0000200000000400 R08: 00007ffc08e3a5d0 R09: 0000000000804444
R10: 0000000000804444 R11: 0000000000000246 R12: 0000200000012500
R13: 00007ffc08e3a590 R14: 0000000000012636 R15: 00002000000004c0
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__gfs2_glock_put+0x384/0x3e0 fs/gfs2/glock.c:274
Code: 3f 48 89 de e8 7d 0f ff ff eb 26 e8 b6 38 c3 fd e9 30 fe ff ff e8 ac 38 c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 2d df ff ff 90 <0f> 0b e8 95 38 c3 fd 31 f6 65 ff 0d 8c 02 72 0e 40 0f 94 c5 40 0f
RSP: 0018:ffffc90002a6f408 EFLAGS: 00010246
RAX: 29c52adf4a6b3d00 RBX: ffff88801131cfd8 RCX: ffff8880002c0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffc90002a6ecc7 R09: 1ffff9200054dd98
R10: dffffc0000000000 R11: fffff5200054dd99 R12: dffffc0000000000
R13: 1ffff11007cab015 R14: ffff88803e558000 R15: ffff88801131d2c8
FS:  0000555578b1a500(0000) GS:ffff88808d732000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd59ca21eb8 CR3: 00000000126a6000 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.

      reply	other threads:[~2025-11-05  5:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  6:44 [syzbot] [gfs2?] kernel BUG in __gfs2_glock_put (2) syzbot
2025-11-05  5:01 ` 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=690ada23.050a0220.baf87.0008.GAE@google.com \
    --to=syzbot+ef4ad020dc976d178975@syzkaller.appspotmail.com \
    --cc=agruenba@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.