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,
julius@bairaktaris.de, ericwouds@gmail.com, razor@blackwall.org
Subject: Re: [PATCH nf-next] netfilter: flowtable: teardown flow reaching bridge port on fdb updates
Date: Thu, 15 Oct 2026 20:07:10 +0800 [thread overview]
Message-ID: <202610152010.2EqEudOw-lkp@intel.com> (raw)
In-Reply-To: <20261014210256.1573072-1-pablo@netfilter.org>
Hi Pablo,
kernel test robot noticed the following build errors:
[auto build test ERROR on nf-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Pablo-Neira-Ayuso/netfilter-flowtable-teardown-flow-reaching-bridge-port-on-fdb-updates/20261014-230256
base: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next.git main
patch link: https://lore.kernel.org/r/20261014210256.1573072-1-pablo%40netfilter.org
patch subject: [PATCH nf-next] netfilter: flowtable: teardown flow reaching bridge port on fdb updates
config: hexagon-randconfig-1000-20261015 (https://download.01.org/0day-ci/archive/20261015/202610152010.2EqEudOw-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 6719b9e31d6a93099612c474eec76d9f41d0275a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261015/202610152010.2EqEudOw-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/202610152010.2EqEudOw-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/bridge/br_nf_utils.c:32:6: error: assigning to 'const struct net_bridge_port *' from incompatible type 'typeof_unqual (f->dst)' (aka 'struct net_bridge_dst')
32 | dst = READ_ONCE(f->dst);
| ^ ~~~~~~~~~~~~~~~~~
1 error generated.
vim +32 net/bridge/br_nf_utils.c
8
9 static bool nf_br_fdb_valid_dst(struct net *net, int ifindex,
10 const unsigned char *addr, __u16 vid)
11 {
12 const struct net_bridge_port *dst;
13 struct net_device *dev, *upper;
14 struct net_bridge_fdb_entry *f;
15 struct net_bridge *br;
16
17 rcu_read_lock();
18 dev = dev_get_by_index_rcu(net, ifindex);
19 if (!dev || !netif_is_bridge_port(dev))
20 goto out;
21
22 upper = netdev_master_upper_dev_get_rcu(dev);
23 if (!upper)
24 goto out;
25
26 br = netdev_priv(upper);
27
28 f = br_fdb_find_rcu(br, addr, vid);
29 if (!f)
30 goto out;
31
> 32 dst = READ_ONCE(f->dst);
33 if (dst && dst->dev->ifindex == ifindex) {
34 rcu_read_unlock();
35 return true;
36 }
37 out:
38 rcu_read_unlock();
39
40 return false;
41 }
42
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-10-15 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 21:02 [PATCH nf-next] netfilter: flowtable: teardown flow reaching bridge port on fdb updates Pablo Neira Ayuso
2026-10-14 22:00 ` Julius Bairaktaris
2026-10-14 22:19 ` Pablo Neira Ayuso
2026-10-15 11:56 ` kernel test robot
2026-10-15 12:07 ` kernel test robot [this message]
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=202610152010.2EqEudOw-lkp@intel.com \
--to=lkp@intel.com \
--cc=ericwouds@gmail.com \
--cc=julius@bairaktaris.de \
--cc=llvm@lists.linux.dev \
--cc=netfilter-devel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.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 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.