From: syzbot ci <syzbot+cib8d2bcab3a0987ad@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop
Date: Wed, 10 Dec 2025 10:19:03 -0800 [thread overview]
Message-ID: <6939b997.050a0220.4004e.01c3.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] net: sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop
https://lore.kernel.org/all/20251210172554.1071864-1-jhs@mojatatu.com
* [PATCH RFC net 1/1] net: sched: Fix ethx:ingress -> ethy:egress -> ethx:ingress mirred loop
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/785801a9-be3c-4519-8b86-36e6e4fe755f
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: 8f7aa3d3c7323f4ca2768a9e74ebbe359c4f8f88
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/6396437f-7fc3-43a9-8d8e-1cfd6ffca37b/config
drivers/net/wireguard/queueing.h:96:2: error: call to undeclared function 'skb_reset_redirect'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
net/netfilter/nft_fwd_netdev.c:34:2: error: call to undeclared function 'skb_set_redirected'; 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:
[daniel@iogearbox.net davem@davemloft.net dcaratti@redhat.com edumazet@google.com horms@kernel.org jhs@mojatatu.com jiri@resnulli.us kuba@kernel.org lariel@nvidia.com netdev@vger.kernel.org pabeni@redhat.com pablo@netfilter.org victor@mojatatu.com xiyou.wangcong@gmail.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-12-10 18:19 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=6939b997.050a0220.4004e.01c3.GAE@google.com \
--to=syzbot+cib8d2bcab3a0987ad@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.