From: kernel test robot <lkp@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Cc: 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 19:56:44 +0800 [thread overview]
Message-ID: <202610151944.1oSb04pC-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: nios2-randconfig-1000-20261015 (https://download.01.org/0day-ci/archive/20261015/202610151944.1oSb04pC-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261015/202610151944.1oSb04pC-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/202610151944.1oSb04pC-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from ./arch/nios2/include/generated/asm/rwonce.h:1,
from include/linux/compiler.h:369,
from include/linux/build_bug.h:5,
from include/linux/container_of.h:5,
from include/linux/list.h:5,
from include/linux/module.h:12,
from net/bridge/br_nf_utils.c:2:
net/bridge/br_nf_utils.c: In function 'nf_br_fdb_valid_dst':
>> include/asm-generic/rwonce.h:48:1: error: incompatible types when assigning to type 'const struct net_bridge_port *' from type 'struct net_bridge_dst'
48 | ({ \
| ^
net/bridge/br_nf_utils.c:32:15: note: in expansion of macro 'READ_ONCE'
32 | dst = READ_ONCE(f->dst);
| ^~~~~~~~~
vim +48 include/asm-generic/rwonce.h
e506ea451254ab Will Deacon 2019-10-15 46
e506ea451254ab Will Deacon 2019-10-15 47 #define READ_ONCE(x) \
e506ea451254ab Will Deacon 2019-10-15 @48 ({ \
e506ea451254ab Will Deacon 2019-10-15 49 compiletime_assert_rwonce_type(x); \
3c9184109e78ea Will Deacon 2019-10-30 50 __READ_ONCE(x); \
e506ea451254ab Will Deacon 2019-10-15 51 })
e506ea451254ab Will Deacon 2019-10-15 52
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-10-15 11:57 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 [this message]
2026-10-15 12:07 ` kernel test robot
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=202610151944.1oSb04pC-lkp@intel.com \
--to=lkp@intel.com \
--cc=ericwouds@gmail.com \
--cc=julius@bairaktaris.de \
--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.