From: kernel test robot <lkp@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
fw@strlen.de, ericwouds@gmail.com
Subject: Re: [PATCH nf-next,v5] netfilter: flowtable: initial bridge support
Date: Thu, 6 Aug 2026 09:27:39 +0800 [thread overview]
Message-ID: <202608060907.TfJm13ei-lkp@intel.com> (raw)
In-Reply-To: <20260713123650.1656551-1-pablo@netfilter.org>
Hi Pablo,
kernel test robot noticed the following build errors:
[auto build test ERROR on netfilter-nf/main]
[also build test ERROR on nf-next/main linus/master v7.2-rc6 next-20260805]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Pablo-Neira-Ayuso/netfilter-flowtable-initial-bridge-support/20260805-124729
base: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git main
patch link: https://lore.kernel.org/r/20260713123650.1656551-1-pablo%40netfilter.org
patch subject: [PATCH nf-next,v5] netfilter: flowtable: initial bridge support
config: loongarch-randconfig-001-20260806 (https://download.01.org/0day-ci/archive/20260806/202608060907.TfJm13ei-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260806/202608060907.TfJm13ei-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608060907.TfJm13ei-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/netfilter/nft_flow_offload.c:153:21: error: call to undeclared function 'nf_bridge_info_exists'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
153 | if (!pkt->flags || nf_bridge_info_exists(pkt->skb))
| ^
1 error generated.
vim +/nf_bridge_info_exists +153 net/netfilter/nft_flow_offload.c
138
139 static void nft_flow_offload_bridge_eval(const struct nft_expr *expr,
140 struct nft_regs *regs,
141 const struct nft_pktinfo *pkt)
142 {
143 struct nft_flow_offload *priv = nft_expr_priv(expr);
144 struct nf_flowtable *flowtable = &priv->flowtable->data;
145 struct tcphdr _tcph, *tcph = NULL;
146 enum ip_conntrack_info ctinfo;
147 struct flow_offload *flow;
148 enum ip_conntrack_dir dir;
149 struct nf_conn *ct;
150 int ret;
151
152 /* Is this a non-IP packet or br_netfilter? If so, skip. */
> 153 if (!pkt->flags || nf_bridge_info_exists(pkt->skb))
154 goto out;
155
156 ct = nf_ct_get(pkt->skb, &ctinfo);
157 if (!ct || !nf_ct_is_confirmed(ct))
158 goto out;
159
160 /* Unlikely, conntrack bridge should not see neither helpers nor NAT in
161 * the bridge forward path.
162 */
163 if (nf_ct_ext_exist(ct, NF_CT_EXT_HELPER) ||
164 ct->status & (IPS_SEQ_ADJUST | IPS_NAT_CLASH))
165 goto out;
166
167 switch (ct->tuplehash[IP_CT_DIR_ORIGINAL].tuple.dst.protonum) {
168 case IPPROTO_TCP:
169 tcph = skb_header_pointer(pkt->skb, nft_thoff(pkt),
170 sizeof(_tcph), &_tcph);
171 if (unlikely(!tcph || tcph->fin || tcph->rst ||
172 !nf_conntrack_tcp_established(ct)))
173 goto out;
174 break;
175 case IPPROTO_UDP:
176 break;
177 default:
178 goto out;
179 }
180
181 if (test_and_set_bit(IPS_OFFLOAD_BIT, &ct->status))
182 goto out;
183
184 flow = flow_offload_alloc(ct);
185 if (!flow)
186 goto err_flow_forward;
187
188 dir = CTINFO2DIR(ctinfo);
189 if (nft_flow_bridge(flow, pkt, dir, priv->flowtable) < 0)
190 goto err_flow_add;
191
192 if (tcph)
193 flow_offload_ct_tcp(ct);
194
195 __set_bit(NF_FLOW_HW_BIDIRECTIONAL, &flow->flags);
196 ret = flow_offload_add(flowtable, flow);
197 if (ret < 0)
198 goto err_flow_add;
199
200 return;
201
202 err_flow_add:
203 flow_offload_free(flow);
204 err_flow_forward:
205 clear_bit(IPS_OFFLOAD_BIT, &ct->status);
206 out:
207 regs->verdict.code = NFT_BREAK;
208 }
209
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-08-06 1:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260713123650.1656551-1-pablo@netfilter.org>]
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=202608060907.TfJm13ei-lkp@intel.com \
--to=lkp@intel.com \
--cc=ericwouds@gmail.com \
--cc=fw@strlen.de \
--cc=llvm@lists.linux.dev \
--cc=netfilter-devel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pablo@netfilter.org \
/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