mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: CJ <firefly0158@163.com>
To: agruenba@redhat.com
Cc: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: INFO: task hung in gfs2_glock_nq on v7.3-rc2
Date: Fri, 13 Nov 2026 11:26:01 +0800 (CST)	[thread overview]
Message-ID: <2b1d6f3b.2f1d.1a1d2f0d896.Coremail.firefly0158@163.com> (raw)


Hi,


syzbot reported "INFO: task hung in gfs2_glock_nq" on Linux 6.1. The same failure is still
reproducible on v7.3-rc2 with the adapted reproducer described below.


The reproducer mounts a crafted GFS2 meta image, keeps a directory descriptor alive, and performs path lookups in the mounted filesystem. The adapted syz program keeps the image and mount call unchanged and adds explicit openat lookups for GFS2 meta entries, making the recorded lookup path deterministic.


The target console reports a hung task blocked in gfs2_glock_wait and gfs2_glock_nq, reached from __gfs2_lookup through lookup_slow.


The lookup remains blocked while acquiring the directory glock. The report shows a reproducible wait condition, not a bisected root cause.


This is a follow-up for the existing syzbot report https://syzkaller.appspot.com/bug?extid=90f9c53a8e1181aa3f4b, not a
bisected root cause. The target report shares
11 key frames with the source crash report.


Reproducer:
 syz reproducer: https://pastebin.com/raw/11YeJKmY


console output: https://pastebin.com/raw/wze6L4ca
kernel config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=872c04466179833f


Kernel:
  HEAD commit: df2908090cda368b01ff43709f51890076c56157
  git tree: linux-stable
  kernel version: 7.3.0-rc2
  tested tag: v7.3-rc2


Let me know if you need more details or testing.


Thanks.


                 reply	other threads:[~2026-11-13  3: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=2b1d6f3b.2f1d.1a1d2f0d896.Coremail.firefly0158@163.com \
    --to=firefly0158@163.com \
    --cc=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®