From: syzbot ci <syzbot+cia5e6e396ddec2565@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: igmp: use copy-on-write RCU updates in ip_mc_source()
Date: Mon, 02 Nov 2026 13:13:08 -0800 [thread overview]
Message-ID: <6ae8fce4.52c4c7f9.b7231.0004.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] igmp: use copy-on-write RCU updates in ip_mc_source()
https://lore.kernel.org/all/20261102095312.47767-1-18983559317@163.com
* [PATCH net v1] igmp: use copy-on-write RCU updates in ip_mc_source()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/03228251-9799-4e5a-8f98-a8e37eb3c89f
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: 209108a5456171ab430e25b54b2dfe083455bfb6
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/a8f5c308-a81f-4c46-8bef-b7d2c3d0efbc/config
net/ipv4/igmp.c:2646:1: error: function definition is not allowed here
net/ipv4/igmp.c:2737:1: error: function definition is not allowed here
net/ipv4/igmp.c:2797:1: error: function definition is not allowed here
net/ipv4/igmp.c:2846:1: error: function definition is not allowed here
net/ipv4/igmp.c:2893:1: error: function definition is not allowed here
net/ipv4/igmp.c:2919:1: error: function definition is not allowed here
net/ipv4/igmp.c:2972:1: error: function definition is not allowed here
net/ipv4/igmp.c:2994:1: error: function definition is not allowed here
net/ipv4/igmp.c:3013:1: error: function definition is not allowed here
net/ipv4/igmp.c:3023:1: error: function definition is not allowed here
net/ipv4/igmp.c:3029:1: error: function definition is not allowed here
net/ipv4/igmp.c:3041:1: error: function definition is not allowed here
net/ipv4/igmp.c:3050:1: error: function definition is not allowed here
net/ipv4/igmp.c:3089:11: error: use of undeclared identifier 'igmp_mc_seq_start'; did you mean 'mr_mfc_seq_start'?
net/ipv4/igmp.c:3090:10: error: use of undeclared identifier 'igmp_mc_seq_next'
net/ipv4/igmp.c:3091:10: error: use of undeclared identifier 'igmp_mc_seq_stop'; did you mean 'igmp_mc_seq_ops'?
net/ipv4/igmp.c:3092:10: error: use of undeclared identifier 'igmp_mc_seq_show'; did you mean 'igmp_mc_seq_ops'?
net/ipv4/igmp.c:3105:1: error: function definition is not allowed here
net/ipv4/igmp.c:3134:1: error: function definition is not allowed here
***
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:
[18983559317@163.com 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]
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-11-02 21:13 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=6ae8fce4.52c4c7f9.b7231.0004.GAE@google.com \
--to=syzbot+cia5e6e396ddec2565@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