From: syzbot <syzbot+fa7122891ab9e0bbc6a7@syzkaller.appspotmail.com>
To: kriish.sharma2006@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] general protection fault in gfs2_print_dbg (3)
Date: Tue, 16 Sep 2025 12:36:04 -0700 [thread overview]
Message-ID: <68c9bc24.050a0220.2ff435.042b.GAE@google.com> (raw)
In-Reply-To: <CAL4kbRPknFFpz9OHU8GruOU-berH3tTqJZZSivzR0mXhAOinHg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+fa7122891ab9e0bbc6a7@syzkaller.appspotmail.com
Tested-by: syzbot+fa7122891ab9e0bbc6a7@syzkaller.appspotmail.com
Tested on:
commit: 05af7647 Add linux-next specific files for 20250916
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15f9b762580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e269dbc7717119a2
dashboard link: https://syzkaller.appspot.com/bug?extid=fa7122891ab9e0bbc6a7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1211f762580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-09-16 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL4kbRPknFFpz9OHU8GruOU-berH3tTqJZZSivzR0mXhAOinHg@mail.gmail.com>
2025-09-16 19:36 ` syzbot [this message]
[not found] <CAL4kbROsdpZx0V8p3imCd4s=PLQuxCg4wtDzte2Z7ik40rGgyg@mail.gmail.com>
2025-09-16 21:09 ` [syzbot] [gfs2?] general protection fault in gfs2_print_dbg (3) syzbot
[not found] <CAL4kbRNO9ciS9zWA3bjZOEbseEvHHM=DxtNae=phjzYTDEpEBg@mail.gmail.com>
2025-09-16 20:16 ` syzbot
2025-09-15 18:18 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=68c9bc24.050a0220.2ff435.042b.GAE@google.com \
--to=syzbot+fa7122891ab9e0bbc6a7@syzkaller.appspotmail.com \
--cc=kriish.sharma2006@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox