From: syzbot <syzbot+642d0561f78362d67d3f@syzkaller.appspotmail.com>
To: jie.wang@intel.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] BUG: sleeping function called from invalid context in lockref_get_not_dead
Date: Wed, 22 Apr 2026 20:38:02 -0700 [thread overview]
Message-ID: <69e9941a.a00a0220.17a17.0035.GAE@google.com> (raw)
In-Reply-To: <20260423105200.115983-1-jie.wang@intel.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+642d0561f78362d67d3f@syzkaller.appspotmail.com
Tested-by: syzbot+642d0561f78362d67d3f@syzkaller.appspotmail.com
Tested on:
commit: 30e80560 gfs2: fix quota init duplicate scan
git tree: https://github.com/wangjie220704/linux.git fix/gfs2_quota_642d_v5
console output: https://syzkaller.appspot.com/x/log.txt?x=1224df16580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c444e47ccaf09c36
dashboard link: https://syzkaller.appspot.com/bug?extid=642d0561f78362d67d3f
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-04-23 3:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260417163634.1274467-1-jie.wang@intel.com>
2026-04-17 9:37 ` [syzbot] [gfs2?] BUG: sleeping function called from invalid context in lockref_get_not_dead syzbot
2026-04-21 15:01 ` Jie Wang
2026-04-21 8:30 ` syzbot
2026-04-23 10:52 ` Jie Wang
2026-04-23 3:38 ` syzbot [this message]
[not found] <20260417161758.1270120-1-jie.wang@intel.com>
2026-04-17 9:21 ` syzbot
[not found] <20260417134812.1019932-1-jie.wang@intel.com>
2026-04-17 6:36 ` syzbot
2026-04-15 11:37 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=69e9941a.a00a0220.17a17.0035.GAE@google.com \
--to=syzbot+642d0561f78362d67d3f@syzkaller.appspotmail.com \
--cc=jie.wang@intel.com \
--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.