From: syzbot ci <syzbot+ci77d1175af83fb6f9@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: vxlan: reject adding a remote to a nexthop fdb entry
Date: Wed, 28 Oct 2026 12:12:38 -0700 [thread overview]
Message-ID: <6ae24926.563b7334.151a55.006f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v5] vxlan: reject adding a remote to a nexthop fdb entry
https://lore.kernel.org/all/20261028111626.3460759-1-bsdhenrymartin@gmail.com
* [PATCH net v5 1/2] vxlan: reject adding a remote to a nexthop fdb entry
* [PATCH net v5 2/2] vxlan: reject VNI add when the default fdb entry is nexthop-backed
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/f7fd20f7-d301-4fed-9566-697656205c6d
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: c03c1a14507dfaf8b856c2608f9ac216021fc222
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/7d3d2084-a9fe-4c35-95b7-30c5a8ad00dc/config
drivers/net/vxlan/vxlan_vnifilter.c:746:23: error: use of undeclared identifier 'cfg'
***
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:
[andrew@lunn.ch atenart@redhat.com bsdhenrymartin@gmail.com davem@davemloft.net edumazet@kernel.org ferruh.yigit@amd.com horms@kernel.org i.maximets@ovn.org idosch@nvidia.com kuba@kernel.org kuniyu@google.com linux-kernel@vger.kernel.org netdev@vger.kernel.org pabeni@redhat.com petrm@nvidia.com qotmddnjs@gmail.com stable@vger.kernel.org]
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-28 19:12 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=6ae24926.563b7334.151a55.006f.GAE@google.com \
--to=syzbot+ci77d1175af83fb6f9@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