From: syzbot ci <syzbot+ci6b62cc4ae8b262c5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: netfilter: conntrack: remove some code
Date: Thu, 21 May 2026 22:54:44 -0700 [thread overview]
Message-ID: <6a0fefa4.170a0220.2e5ec6.0004.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] netfilter: conntrack: remove some code
https://lore.kernel.org/all/20260522050140.4838-1-fw@strlen.de
* [PATCH nf-next 1/5] netfilter: nf_conntrack_helper: do not hash by tuple
* [PATCH nf-next 2/5] netfilter: conntrack: get rid of tuple in helper definitions
* [PATCH nf-next 3/5] netfilter: nf_conntrack: switch to static registration
* [PATCH nf-next 4/5] netfilter: remove obsolete nf_ct_helper_init api
* [PATCH nf-next 5/5] netfilter: conntrack: add deprecation warnings for irc and pptp trackers
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/6b7dd605-be91-42de-a939-b82234442904
***
kernel build error
tree: nf
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netfilter/nf.git
base: ab1513597c6cf17cd1ad2a21e3b045421b48e022
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/52edd1a1-56d7-4133-811a-d2be41816921/config
net/netfilter/nf_conntrack_ovs.c:31:14: error: no member named 'tuple' in 'struct nf_conntrack_helper'
net/netfilter/nf_conntrack_ovs.c:32:14: error: no member named 'tuple' in 'struct nf_conntrack_helper'
net/netfilter/nf_conntrack_ovs.c:60:14: error: no member named 'tuple' in 'struct nf_conntrack_helper'
net/sched/act_ct.c:1527:52: error: no member named 'tuple' in 'struct nf_conntrack_helper'
net/sched/act_ct.c:1528:51: error: no member named 'tuple' in 'struct nf_conntrack_helper'
***
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:
[fw@strlen.de netfilter-devel@vger.kernel.org]
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-05-22 5:54 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=6a0fefa4.170a0220.2e5ec6.0004.GAE@google.com \
--to=syzbot+ci6b62cc4ae8b262c5@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