From: syzbot ci <syzbot+cid6d1c421f4b40ac2@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: esp: Consolidate esp4 and esp6.
Date: Tue, 21 Oct 2025 23:37:43 -0700 [thread overview]
Message-ID: <68f87bb7.a70a0220.3bf6c6.0012.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] esp: Consolidate esp4 and esp6.
https://lore.kernel.org/all/aPhzm0lzMXGSpf22@secunet.com
* [PATCH RFC ipsec-next] esp: Consolidate esp4 and esp6.
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/94fdf624-7c77-4b72-9ac3-4ffcfc0e8bfc
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 88224095b4e512b027289183f432c0e84925d648
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/4414521b-8681-421d-817e-7eebe68995cb/config
net/ipv6/esp6.c:67:15: error: call to undeclared function 'csum_ipv6_magic'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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.
The email will later be sent to:
[devel@linux-ipsec.org netdev@vger.kernel.org steffen.klassert@secunet.com]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-10-22 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 6:37 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-26 18:53 [moderation/CI] Re: esp: Consolidate esp4 and esp6 syzbot ci
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=68f87bb7.a70a0220.3bf6c6.0012.GAE@google.com \
--to=syzbot+cid6d1c421f4b40ac2@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