From: syzbot ci <syzbot+ci0dfcdc44ab9eadd7@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: Fix Hole-196 vulnerability by dropping unicast ARP/IP in L2 BMC
Date: Mon, 26 Oct 2026 12:48:02 -0700 [thread overview]
Message-ID: <6adfae72.768774f5.3237ab.000f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] net: Fix Hole-196 vulnerability by dropping unicast ARP/IP in L2 BMC
https://lore.kernel.org/all/20261026150539.1357037-1-starchang@google.com
* [PATCH net v3] net: Fix Hole-196 vulnerability by dropping unicast ARP/IP in L2 BMC
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/ee0be733-8410-476d-be92-1602ae89d8f4
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: d3c157b4cdffd14604c2d8435e279761c511bac2
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/027a790e-c04b-4f75-90b1-1e89288623c1/config
net/ipv4/ip_input.c:483:26: warning: missing terminating '"' character [-Winvalid-pp-token]
net/ipv4/ip_input.c:484:1: warning: missing terminating '"' character [-Winvalid-pp-token]
net/ipv4/ip_input.c:483:26: error: expected ')'
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[davem@davemloft.net dsahern@kernel.org edumazet@google.com horms@kernel.org idosch@nvidia.com kuba@kernel.org linux-kernel@vger.kernel.org netdev@vger.kernel.org pabeni@redhat.com starchang@google.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-10-26 19:48 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=6adfae72.768774f5.3237ab.000f.GAE@google.com \
--to=syzbot+ci0dfcdc44ab9eadd7@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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