From: kernel test robot <lkp@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH nf-next v2 3/3] netfilter: nft_set_pipapo: Use nested-BH locking for nft_pipapo_scratch
Date: Tue, 19 Aug 2025 23:49:46 +0800 [thread overview]
Message-ID: <202508192340.c0ABcR8U-lkp@intel.com> (raw)
In-Reply-To: <20250815160937.1192748-4-bigeasy@linutronix.de>
Hi Sebastian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on netfilter-nf/main]
[also build test WARNING on linus/master v6.17-rc2 next-20250819]
[cannot apply to nf-next/master horms-ipvs/master]
[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/Sebastian-Andrzej-Siewior/netfilter-nft_set_pipapo-Store-real-pointer-adjust-later/20250816-001334
base: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git main
patch link: https://lore.kernel.org/r/20250815160937.1192748-4-bigeasy%40linutronix.de
patch subject: [PATCH nf-next v2 3/3] netfilter: nft_set_pipapo: Use nested-BH locking for nft_pipapo_scratch
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250819/202508192340.c0ABcR8U-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250819/202508192340.c0ABcR8U-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/202508192340.c0ABcR8U-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/netfilter/nft_set_pipapo_avx2.c:1176:10: warning: expression which evaluates to zero treated as a null pointer constant of type 'const struct nft_set_ext *' [-Wnon-literal-null-conversion]
1176 | return false;
| ^~~~~
1 warning generated.
vim +1176 net/netfilter/nft_set_pipapo_avx2.c
1134
1135 /**
1136 * nft_pipapo_avx2_lookup() - Lookup function for AVX2 implementation
1137 * @net: Network namespace
1138 * @set: nftables API set representation
1139 * @key: nftables API element representation containing key data
1140 *
1141 * For more details, see DOC: Theory of Operation in nft_set_pipapo.c.
1142 *
1143 * This implementation exploits the repetitive characteristic of the algorithm
1144 * to provide a fast, vectorised version using the AVX2 SIMD instruction set.
1145 *
1146 * Return: true on match, false otherwise.
1147 */
1148 const struct nft_set_ext *
1149 nft_pipapo_avx2_lookup(const struct net *net, const struct nft_set *set,
1150 const u32 *key)
1151 {
1152 struct nft_pipapo *priv = nft_set_priv(set);
1153 const struct nft_set_ext *ext = NULL;
1154 struct nft_pipapo_scratch *scratch;
1155 u8 genmask = nft_genmask_cur(net);
1156 const struct nft_pipapo_match *m;
1157 const struct nft_pipapo_field *f;
1158 unsigned long *res, *fill, *map;
1159 const u8 *rp = (const u8 *)key;
1160 bool map_index;
1161 int i;
1162
1163 local_bh_disable();
1164
1165 if (unlikely(!irq_fpu_usable())) {
1166 ext = nft_pipapo_lookup(net, set, key);
1167
1168 local_bh_enable();
1169 return ext;
1170 }
1171
1172 m = rcu_dereference(priv->match);
1173 scratch = *raw_cpu_ptr(m->scratch);
1174 if (unlikely(!scratch)) {
1175 local_bh_enable();
> 1176 return false;
1177 }
1178 __local_lock_nested_bh(&scratch->bh_lock);
1179 /* Note that we don't need a valid MXCSR state for any of the
1180 * operations we use here, so pass 0 as mask and spare a LDMXCSR
1181 * instruction.
1182 */
1183 kernel_fpu_begin_mask(0);
1184
1185 map_index = scratch->map_index;
1186 map = NFT_PIPAPO_LT_ALIGN(&scratch->__map[0]);
1187 res = map + (map_index ? m->bsize_max : 0);
1188 fill = map + (map_index ? 0 : m->bsize_max);
1189
1190 pipapo_resmap_init_avx2(m, res);
1191
1192 nft_pipapo_avx2_prepare();
1193
1194 next_match:
1195 nft_pipapo_for_each_field(f, i, m) {
1196 bool last = i == m->field_count - 1, first = !i;
1197 int ret = 0;
1198
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-19 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 16:09 [PATCH nf-next v2 0/3] netfilter: nft_set_pipapo: Use nested-BH locking for nft_pipapo_scratch Sebastian Andrzej Siewior
2025-08-15 16:09 ` [PATCH nf-next v2 1/3] netfilter: nft_set_pipapo: Store real pointer, adjust later Sebastian Andrzej Siewior
2025-08-15 16:09 ` [PATCH nf-next v2 2/3] netfilter: nft_set_pipapo_avx2: Drop the comment regarding protection Sebastian Andrzej Siewior
2025-08-15 16:09 ` [PATCH nf-next v2 3/3] netfilter: nft_set_pipapo: Use nested-BH locking for nft_pipapo_scratch Sebastian Andrzej Siewior
2025-08-16 14:25 ` Florian Westphal
2025-08-18 9:11 ` Sebastian Andrzej Siewior
2025-08-18 9:24 ` Florian Westphal
2025-08-18 9:56 ` Sebastian Andrzej Siewior
2025-08-19 15:49 ` kernel test robot [this message]
2025-08-21 6:03 ` kernel test robot
2025-08-16 15:15 ` [PATCH nf-next v2 0/3] " Florian Westphal
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=202508192340.c0ABcR8U-lkp@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.