From: syzbot ci <syzbot+ciee69b98a22fc6f04@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: conntrack expectation fixes
Date: Sat, 21 Mar 2026 05:00:56 -0700 [thread overview]
Message-ID: <69be8878.050a0220.3bf4de.004f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] conntrack expectation fixes
https://lore.kernel.org/all/20260320125947.305117-1-pablo@netfilter.org
* [PATCH nf 1/5] netfilter: nf_conntrack_expect: honor expectation helper field
* [PATCH nf 2/5] netfilter: nf_conntrack_expect: use expect->helper
* [PATCH nf 3/5] netfilter: ctnetlink: ensure safe access to master conntrack
* [PATCH nf 4/5] netfilter: nf_conntrack_expect: store netns and zone in expectation
* [PATCH nf 5/5] netfilter: nf_conntrack_expect: skip expectations in other netns via proc
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/d856b4aa-722b-4363-9a8e-90b54d9245a4
***
kernel build error
tree: nf
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netfilter/nf.git
base: e7577a06ae28287ca415aec5c12277e3a80ee372
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/9222913b-669f-4a16-b489-589958297c6e/config
net/core/flow_dissector.c:36:2: error: embedding a #include directive within macro arguments is not supported
net/core/flow_dissector.c:38:2: error: embedding a #include directive within macro arguments is not supported
./include/net/netfilter/nf_conntrack_core.h:90:3: error: unterminated function-like macro invocation
net/core/flow_dissector.c:2101:45: error: expected expression
net/core/flow_dissector.c:2101:45: error: expected '}'
net/netfilter/nf_conntrack_core.c:42:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:43:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:44:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:45:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:46:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:47:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:48:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:49:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:50:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:51:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:52:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:53:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:55:2: error: embedding a #include directive within macro arguments is not supported
net/netfilter/nf_conntrack_core.c:2827:47: error: expected expression
net/netfilter/nf_conntrack_core.c:2827:47: error: expected '}'
***
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:
[fw@strlen.de netfilter-devel@vger.kernel.org pablo@netfilter.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-03-21 12:00 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=69be8878.050a0220.3bf4de.004f.GAE@google.com \
--to=syzbot+ciee69b98a22fc6f04@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.