From: syzbot <syzbot+a2a3b519de727b0f7903@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
zlatistiv@gmail.com
Subject: Re: [syzbot] [net?] kernel BUG in ipgre_header (3)
Date: Sun, 09 Nov 2025 12:00:02 -0800 [thread overview]
Message-ID: <6910f2c2.a70a0220.22f260.00c4.GAE@google.com> (raw)
In-Reply-To: <CAHjv_atAdhZoCs=C1CFnq2ZdqycdaQnDi5MDUGFo5J_2AAdHAQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a2a3b519de727b0f7903@syzkaller.appspotmail.com
Tested-by: syzbot+a2a3b519de727b0f7903@syzkaller.appspotmail.com
Tested on:
commit: f850568e Merge tag 'i2c-for-6.18-rc5' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1357517c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486aa0235ebabcac
dashboard link: https://syzkaller.appspot.com/bug?extid=a2a3b519de727b0f7903
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=12d4a412580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-09 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHjv_atAdhZoCs=C1CFnq2ZdqycdaQnDi5MDUGFo5J_2AAdHAQ@mail.gmail.com>
2025-11-09 20:00 ` syzbot [this message]
[not found] <CAHjv_asZ2DhnOf8CV8FFi5oBQ-zEvHLt6zHocM8SavZB-C3cLw@mail.gmail.com>
2025-11-09 19:37 ` [syzbot] [net?] kernel BUG in ipgre_header (3) syzbot
[not found] <CAHjv_avmxaoUvH17xdu+JTw42Dmc70h+xooj1JxsKjQ8Fh3GrA@mail.gmail.com>
2025-11-08 16:19 ` syzbot
[not found] <CAHjv_atXD_F0pMfDS5z36mR=inYx+pnODBLF+oj7uZuBMnK+9g@mail.gmail.com>
2025-10-29 17:40 ` syzbot
2025-10-20 16:32 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=6910f2c2.a70a0220.22f260.00c4.GAE@google.com \
--to=syzbot+a2a3b519de727b0f7903@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zlatistiv@gmail.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