From: syzbot ci <syzbot+ci75222525e6acd9da@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: team: reject CAN and IEEE 802.15.4 devices in team_port_add
Date: Wed, 29 Jul 2026 15:46:21 -0700 [thread overview]
Message-ID: <6a6a82bd.57649fcc.360844.0008.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] team: reject CAN and IEEE 802.15.4 devices in team_port_add
https://lore.kernel.org/all/20260728151240.89434-1-yaojiale02@163.com
* [PATCH v2] team: reject CAN and IEEE 802.15.4 devices in team_port_add
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/e0faf45d-b7b0-483e-96d3-a27fcc248199
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 2bb54b49e9d522f54dc9c0fe10ba40fbc56041c8
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/08aac67c-0bc8-4532-a3e2-acb78eba26e8/config
drivers/net/team/team_core.c:1236:2: error: non-void function does not return a value in all control paths [-Werror,-Wreturn-type]
drivers/net/team/team_core.c:1238:2: error: expected identifier or '('
drivers/net/team/team_core.c:1245:2: error: expected identifier or '('
drivers/net/team/team_core.c:1251:2: error: expected identifier or '('
drivers/net/team/team_core.c:1258:2: error: expected identifier or '('
drivers/net/team/team_core.c:1265:2: error: expected identifier or '('
drivers/net/team/team_core.c:1273:2: error: expected identifier or '('
drivers/net/team/team_core.c:1280:2: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
drivers/net/team/team_core.c:1280:9: error: statement expression not allowed at file scope
drivers/net/team/team_core.c:1282:2: error: expected identifier or '('
drivers/net/team/team_core.c:1285:2: error: unknown type name 'port'
drivers/net/team/team_core.c:1285:6: error: expected identifier or '('
drivers/net/team/team_core.c:1286:2: error: unknown type name 'port'
drivers/net/team/team_core.c:1286:6: error: expected identifier or '('
drivers/net/team/team_core.c:1287:17: error: expected parameter declarator
drivers/net/team/team_core.c:1287:17: error: expected ')'
drivers/net/team/team_core.c:1287:2: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
drivers/net/team/team_core.c:1287:16: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
drivers/net/team/team_core.c:1287:2: error: a function declaration without a prototype is deprecated in all versions of C and is treated as a zero-parameter prototype in C23, conflicting with a previous declaration [-Werror,-Wdeprecated-non-prototype]
***
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 patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[andrew@lunn.ch davem@davemloft.net edumazet@google.com jiri@resnulli.us kuba@kernel.org linux-kernel@vger.kernel.org netdev@vger.kernel.org pabeni@redhat.com yaojiale02@163.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-07-29 22:46 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=6a6a82bd.57649fcc.360844.0008.GAE@google.com \
--to=syzbot+ci75222525e6acd9da@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