Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: kernel test robot <lkp@intel.com>, linux-wireless@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH wireless-next 03/18] wifi: nl80211: avoid rtnl for commands that don't want it
Date: Mon, 05 Oct 2026 07:28:50 +0200	[thread overview]
Message-ID: <1130811ccc70721c60e66c3038bf1ec517af1cb4.camel@sipsolutions.net> (raw)
In-Reply-To: <202610051243.rHmDLV0g-lkp@intel.com>

On Mon, 2026-10-05 at 12:18 +0800, kernel test robot wrote:
> 
> > > 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))) {
>          |              ^~~~

Yes ... noticed that too, just slightly too late.

>    net/wireless/nl80211.c:238:27: note: initialize the variable 'wdev' to silence this warning
>      238 |         struct wireless_dev *wdev;
>          |                                  ^
>          |                                   = NULL

That'd be pointless.

>  > 244		    (wdev->netdev && !net_eq(dev_net(wdev->netdev), netns))) {

that line

>    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;

needs to move here.

johannes

  reply	other threads:[~2026-10-05  5:28 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
2026-10-05  5:28     ` Johannes Berg [this message]
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=1130811ccc70721c60e66c3038bf1ec517af1cb4.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox