From: syzbot ci <syzbot+ci25a2c7e771ade7d6@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: netfilter: conntrack: remove obsolete module parameters
Date: Fri, 26 Jun 2026 12:01:16 -0700 [thread overview]
Message-ID: <6a3ecc7c.81aa1f09.c949.0000.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] netfilter: conntrack: remove obsolete module parameters
https://lore.kernel.org/all/20260626123131.23096-1-fw@strlen.de
* [PATCH nf-next 1/3] netfilter: nf_conntrack_helper: do not hash by tuple
* [PATCH nf-next 2/3] netfilter: conntrack: get rid of tuple in helper definitions
* [PATCH nf-next 3/3] netfilter: conntrack: remove obsolete module parameters
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/f65c315d-b9f9-4dc6-8d2c-387298720db0
***
kernel build error
tree: nf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netfilter/nf-next.git
base: 805185b7c7a1069e407b6f7b3bc98e44d415f484
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/55c6b0d0-ab03-486a-ac71-edc3a295de8c/config
net/sched/act_ct.c:1530:52: error: no member named 'tuple' in 'struct nf_conntrack_helper'
net/sched/act_ct.c:1531: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-06-26 19:01 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=6a3ecc7c.81aa1f09.c949.0000.GAE@google.com \
--to=syzbot+ci25a2c7e771ade7d6@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.