From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH wireless-next 03/18] wifi: nl80211: avoid rtnl for commands that don't want it
Date: Mon, 5 Oct 2026 12:18:28 +0800 [thread overview]
Message-ID: <202610051243.rHmDLV0g-lkp@intel.com> (raw)
In-Reply-To: <20261004210122.3b67fb1a6a69.I9c4f85fb60160f377a24c1b8e5173966744e5f09@changeid>
Hi Johannes,
kernel test robot noticed the following build warnings:
[auto build test WARNING on wireless-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Johannes-Berg/wifi-cfg80211-track-netdev-running-state-under-wiphy-mutex/20261004-210115
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link: https://lore.kernel.org/r/20261004210122.3b67fb1a6a69.I9c4f85fb60160f377a24c1b8e5173966744e5f09%40changeid
patch subject: [PATCH wireless-next 03/18] wifi: nl80211: avoid rtnl for commands that don't want it
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20261005/202610051243.rHmDLV0g-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 5f609f950d2e80addf5566623013db68394334db)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261005/202610051243.rHmDLV0g-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/202610051243.rHmDLV0g-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/wireless/nl80211.c:244:7: warning: variable 'wdev' is uninitialized when used here [-Wuninitialized]
244 | (wdev->netdev && !net_eq(dev_net(wdev->netdev), netns))) {
| ^~~~
net/wireless/nl80211.c:238:27: note: initialize the variable 'wdev' to silence this warning
238 | struct wireless_dev *wdev;
| ^
| = NULL
1 warning generated.
vim +/wdev +244 net/wireless/nl80211.c
227
228 /*
229 * Lock the given wiphy, put the device and double-check it's
230 * still valid to use.
231 *
232 * Returns with wiphy mutex held unless there was an error.
233 */
234 static struct wireless_dev *
235 nl80211_lock_and_recheck(struct cfg80211_registered_device *rdev,
236 struct net *netns, u32 wdev_id)
237 {
238 struct wireless_dev *wdev;
239
240 wiphy_lock(&rdev->wiphy);
241
242 if (!rdev->wiphy.registered ||
243 !net_eq(wiphy_net(&rdev->wiphy), netns) ||
> 244 (wdev->netdev && !net_eq(dev_net(wdev->netdev), netns))) {
245 wiphy_unlock(&rdev->wiphy);
246 put_device(&rdev->wiphy.dev);
247 return ERR_PTR(-ENODEV);
248 }
249
250 /*
251 * unregistration blocks on wiphy mutex,
252 * so we don't need this now
253 */
254 put_device(&rdev->wiphy.dev);
255
256 if (!wdev_id)
257 return NULL;
258
259 list_for_each_entry(wdev, &rdev->wiphy.wdev_list, list) {
260 if (wdev->identifier == wdev_id)
261 return wdev;
262 }
263 wiphy_unlock(&rdev->wiphy);
264
265 return ERR_PTR(-ENODEV);
266 }
267
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-10-05 4:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 19:01 [PATCH wireless-next 00/18] wifi: further RTNL redux Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 01/18] wifi: cfg80211: track netdev running state under wiphy mutex Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 02/18] wifi: nl80211: allow device lookup under RCU Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 03/18] wifi: nl80211: avoid rtnl for commands that don't want it Johannes Berg
2026-10-04 20:11 ` Johannes Berg
2026-10-05 4:18 ` kernel test robot [this message]
2026-10-05 5:28 ` Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 04/18] wifi: nl80211: don't take rtnl for most dumps Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 05/18] wifi: cfg80211: reg: update channels under wiphy mutex Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 06/18] wifi: cfg80211: reg: set intersected regd " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 07/18] wifi: cfg80211: update channel DFS data " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 08/18] wifi: mac80211_hwsim: call cfg80211 event with " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 09/18] wifi: cfg80211: document wiphy mutex for radar/CAC events Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 10/18] wifi: cfg80211: add a mutex for regulatory/device list Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 11/18] wifi: cfg80211: allow walking wiphy list under cfg80211_mutex Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 12/18] wifi: ath: use freq_reg_info() under RCU Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 13/18] wifi: brcmsmac: " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 14/18] wifi: rtlwifi: " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 15/18] wifi: nl80211: read WMM reg rule " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 16/18] wifi: ath11k: read wiphy regd " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 17/18] wifi: ath12k: " Johannes Berg
2026-10-04 19:01 ` [PATCH wireless-next 18/18] wifi: cfg80211: regulatory: stop using RTNL Johannes Berg
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=202610051243.rHmDLV0g-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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.