From: syzbot <syzbot+fa7122891ab9e0bbc6a7@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: Sending for testing
Date: Tue, 16 Sep 2025 12:10:02 -0700 [thread overview]
Message-ID: <68c9b60a.050a0220.50883.001d.GAE@google.com> (raw)
In-Reply-To: <68c85874.050a0220.50883.0017.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Sending for testing
Author: kriish.sharma2006@gmail.com
#syz test
diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
index b677c0e6b9ab..5fdde7d4a393 100644
--- a/fs/gfs2/glock.c
+++ b/fs/gfs2/glock.c
@@ -2284,10 +2284,21 @@ static void dump_holder(struct seq_file *seq, const
struct gfs2_holder *gh,
if (gh_owner)
comm = gh_owner->comm;
}
- gfs2_print_dbg(seq, "%s H: s:%s f:%s e:%d p:%ld [%s] %pS\n",
- fs_id_buf, state2str(gh->gh_state),
- hflags2str(flags_buf, gh->gh_flags, gh->gh_iflags),
- gh->gh_error, (long)owner_pid, comm, (void *)gh->gh_ip);
+
+ if(seq){
+ gfs2_print_dbg(seq, "%s H: s:%s f:%s e:%d p:%ld [%s] %pS\n",
+ fs_id_buf, state2str(gh->gh_state),
+ hflags2str(flags_buf, gh->gh_flags, gh->gh_iflags),
+ gh->gh_error, (long)owner_pid, comm, (void *)gh->gh_ip);
+ }
+
+ else{
+ gfs2_print_dbg(seq, "%s H: s:%s f:%s e:%d p:%ld [%s] %p\n",
+ fs_id_buf, state2str(gh->gh_state),
+ hflags2str(flags_buf, gh->gh_flags, gh->gh_iflags),
+ gh->gh_error, (long)owner_pid, comm,
+ (void *)gh->gh_ip);
+ }
rcu_read_unlock();
}
--
2.34.1
next prev parent reply other threads:[~2025-09-16 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 18:18 [syzbot] [gfs2?] general protection fault in gfs2_print_dbg (3) syzbot
2025-09-16 19:10 ` syzbot [this message]
2025-09-16 19:48 ` Forwarded: retest linux-next syzbot
2025-09-16 20:39 ` Forwarded: Final testing 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=68c9b60a.050a0220.50883.001d.GAE@google.com \
--to=syzbot+fa7122891ab9e0bbc6a7@syzkaller.appspotmail.com \
--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