gfs2 filesystem and dlm development
 help / color / mirror / Atom feed
From: sanan.hasanou@gmail.com
To: agruenba@redhat.com, gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, contact@pgazz.com
Subject: invalid opcode in do_qc
Date: Fri, 26 Jun 2026 14:26:32 -0700 (PDT)	[thread overview]
Message-ID: <6a3eee88.87857ece.10923b.6809@mx.google.com> (raw)

Good day, dear maintainers,

We found a bug using a modified version of syzkaller.

Kernel Branch: 7.0-rc1
Kernel Config: <https://drive.google.com/open?id=1pN21FuDB9QSbn_3jaZGO1S5v7x7Qe-yl>
Unfortunately, we don't have any reproducer for this bug yet.
Thank you!

Best regards,
Sanan Hasanov

gfs2: fsid=syz:syz.0: found 1 quota changes
gfs2: fsid=syz:syz.0: fatal assertion failed
Oops: invalid opcode: 0000 [#1] SMP KASAN
CPU: 1 UID: 0 PID: 23411 Comm: syz.9.2470 Tainted: G             L      7.0.0-rc1 #1 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__qd_hold fs/gfs2/quota.c:320 [inline]
RIP: 0010:do_qc+0x5bc/0x5d0 fs/gfs2/quota.c:706
Code: 00 00 00 00 00 fc ff df 48 8b 0c 24 80 3c 01 00 74 0a 48 8b 7c 24 10 e8 22 8b 2b fe 48 8b 44 24 10 48 8b 38 e8 35 66 33 fd 90 <0f> 0b e8 ad fe c7 fd 48 8b 7c 24 10 e8 23 66 33 fd 90 0f 0b f3 0f
RSP: 0018:ffffc9000cc679c8 EFLAGS: 00010246
RAX: 000000000000002c RBX: 1ffff110034ec50a RCX: 9a6c65fb1fe81500
RDX: ffffc90012400000 RSI: 0000000000001797 RDI: 0000000000001798
RBP: ffffffffffffffff R08: ffffc9000cc67747 R09: 1ffff9200198cee8
R10: dffffc0000000000 R11: fffff5200198cee9 R12: ffff88801a7627e0
R13: ffff88801a762850 R14: ffff88801a762870 R15: 0000000000000000
FS:  00007f9a12a336c0(0000) GS:ffff8880be7b6000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32323ffc CR3: 000000003a30d000 CR4: 00000000000006f0
Call Trace:
 <TASK>
 gfs2_quota_change+0x38c/0x800 fs/gfs2/quota.c:1305
 setattr_chown+0x418/0x560 fs/gfs2/inode.c:2072
 gfs2_setattr+0x217/0x3f0 fs/gfs2/inode.c:2124
 notify_change+0xc00/0xf10 fs/attr.c:556
 chown_common+0x441/0x670 fs/open.c:778
 vfs_fchown fs/open.c:843 [inline]
 ksys_fchown+0xe6/0x160 fs/open.c:855
 __do_sys_fchown fs/open.c:860 [inline]
 __se_sys_fchown fs/open.c:858 [inline]
 __x64_sys_fchown+0x7a/0x90 fs/open.c:858
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x11c/0x800 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7f9a11ba3b6d
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9a12a33018 EFLAGS: 00000246 ORIG_RAX: 000000000000005d
RAX: ffffffffffffffda RBX: 00007f9a11e15fa0 RCX: 00007f9a11ba3b6d
RDX: 000000000000ee01 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f9a11c47c3e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9a11e16038 R14: 00007f9a11e15fa0 R15: 00007ffd820de320
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__qd_hold fs/gfs2/quota.c:320 [inline]
RIP: 0010:do_qc+0x5bc/0x5d0 fs/gfs2/quota.c:706
Code: 00 00 00 00 00 fc ff df 48 8b 0c 24 80 3c 01 00 74 0a 48 8b 7c 24 10 e8 22 8b 2b fe 48 8b 44 24 10 48 8b 38 e8 35 66 33 fd 90 <0f> 0b e8 ad fe c7 fd 48 8b 7c 24 10 e8 23 66 33 fd 90 0f 0b f3 0f
RSP: 0018:ffffc9000cc679c8 EFLAGS: 00010246
RAX: 000000000000002c RBX: 1ffff110034ec50a RCX: 9a6c65fb1fe81500
RDX: ffffc90012400000 RSI: 0000000000001797 RDI: 0000000000001798
RBP: ffffffffffffffff R08: ffffc9000cc67747 R09: 1ffff9200198cee8
R10: dffffc0000000000 R11: fffff5200198cee9 R12: ffff88801a7627e0
R13: ffff88801a762850 R14: ffff88801a762870 R15: 0000000000000000
FS:  00007f9a12a336c0(0000) GS:ffff8880be7b6000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32323ffc CR3: 000000003a30d000 CR4: 00000000000006f0

<<<<<<<<<<<<<<< tail report >>>>>>>>>>>>>>>

                 reply	other threads:[~2026-06-26 21:26 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=6a3eee88.87857ece.10923b.6809@mx.google.com \
    --to=sanan.hasanou@gmail.com \
    --cc=agruenba@redhat.com \
    --cc=contact@pgazz.com \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller@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