From: syzbot ci <syzbot+ci8804f03b7e65350e@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: ipvs: Move defense_work to system_dfl_long_wq
Date: Tue, 17 Mar 2026 15:22:51 -0700 [thread overview]
Message-ID: <69b9d43b.050a0220.248e02.015b.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] ipvs: Move defense_work to system_dfl_long_wq
https://lore.kernel.org/all/20260317140100.24993-2-iluceno@suse.de
* [PATCH] ipvs: Move defense_work to system_dfl_long_wq
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/e585d6a4-60a0-4e53-bb7f-02b004020645
***
kernel build error
tree: nf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netfilter/nf-next.git
base: 2c7e63d702f6c4209c5af833308e7fcbc7d4ab17
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/7a5718c9-01b3-46a2-aaa2-4dd1412f64cb/config
net/netfilter/ipvs/ip_vs_ctl.c:237:21: error: use of undeclared identifier 'system_dfl_long_wq'; did you mean 'system_long_wq'?
net/netfilter/ipvs/ip_vs_ctl.c:276:22: error: use of undeclared identifier 'system_dfl_long_wq'; did you mean 'system_long_wq'?
net/netfilter/ipvs/ip_vs_ctl.c:4380:21: error: use of undeclared identifier 'system_dfl_long_wq'; did you mean 'system_long_wq'?
***
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:
[andreas.taschner@suse.com brad.bendily@suse.com brendon.caligari@suse.com cfamullaconrad@suse.com coreteam@netfilter.org davem@davemloft.net edumazet@google.com federico.pinca@suse.com firo.yang@suse.com fw@strlen.de gabriel.bertazi@suse.com horms@kernel.org horms@verge.net.au hvdheuvel@suse.com iluceno@suse.de ja@ssi.bg jdelvare@suse.com kuba@kernel.org linux-kernel@vger.kernel.org lvs-devel@vger.kernel.org marco.crivellari@suse.com mhocko@suse.com mkoutny@suse.com netdev@vger.kernel.org netfilter-devel@vger.kernel.org pabeni@redhat.com pablo@netfilter.org phil@nwl.cc pmladek@suse.com ptesarik@suse.com richard.thompson@suse.com wpreston@suse.com yu.xu@suse.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-03-17 22:22 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=69b9d43b.050a0220.248e02.015b.GAE@google.com \
--to=syzbot+ci8804f03b7e65350e@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