From: syzbot ci <syzbot+ci5cb6cb9b76c3e21a@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: ipvs: fix MTU check for GSO packets in tunnel mode
Date: Thu, 02 Apr 2026 11:26:01 -0700 [thread overview]
Message-ID: <69ceb4b9.050a0220.2dbe29.0006.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] ipvs: fix MTU check for GSO packets in tunnel mode
https://lore.kernel.org/all/tencent_CA2C1C219C99D315086BE55E8654AF7E6009@qq.com
* [PATCH net v2] ipvs: fix MTU check for GSO packets in tunnel mode
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/8a36afb1-bf26-43a7-abda-0fe36dac52b1
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 9147566d801602c9e7fc7f85e989735735bf38ba
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/795d9703-7617-4fa5-8839-73099ccf6fc6/config
net/netfilter/ipvs/ip_vs_xmit.c:115:2: error: non-void function does not return a value in all control paths [-Werror,-Wreturn-type]
net/netfilter/ipvs/ip_vs_xmit.c:115:4: error: expected identifier or '('
net/netfilter/ipvs/ip_vs_xmit.c:119:2: error: expected identifier or '('
net/netfilter/ipvs/ip_vs_xmit.c:120:1: error: extraneous closing brace ('}')
***
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:
[342144303@qq.com coreteam@netfilter.org davem@davemloft.net edumazet@google.com fw@strlen.de horms@verge.net.au ja@ssi.bg kuba@kernel.org linux-kernel@vger.kernel.org lvs-devel@vger.kernel.org netdev@vger.kernel.org netfilter-devel@vger.kernel.org pabeni@redhat.com pablo@netfilter.org phil@nwl.cc]
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-04-02 18:26 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=69ceb4b9.050a0220.2dbe29.0006.GAE@google.com \
--to=syzbot+ci5cb6cb9b76c3e21a@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