[moderation/CI] Re: ipvs: fix MTU check for GSO packets in tunnel mode

[syzbot ci]

syzbot ci has tested the following series

[v2] ipvs: fix MTU check for GSO packets in tunnel mode
https://lore.kernel.org/all/tencent_CA2C1C219C99D3...@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: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@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:
[3421...@qq.com core...@netfilter.org da...@davemloft.net edum...@google.com f...@strlen.de ho...@verge.net.au j...@ssi.bg ku...@kernel.org linux-...@vger.kernel.org lvs-...@vger.kernel.org net...@vger.kernel.org netfilt...@vger.kernel.org pab...@redhat.com pa...@netfilter.org ph...@nwl.cc]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid