From: kernel test robot <lkp@intel.com>
To: johannes@sipsolutions.net
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-wireless@vger.kernel.org,
Issam Hamdi <ih@simonwunderlich.de>,
Kretschmer Mathias <mathias.kretschmer@fit.fraunhofer.de>
Subject: Re: [PATCH] cfg80211: Set the channel definition for the different Wi-Fi modes when starting CAC
Date: Tue, 13 Aug 2024 04:14:05 +0800 [thread overview]
Message-ID: <202408130337.tnSP4Qys-lkp@intel.com> (raw)
In-Reply-To: <20240812120909.2721400-1-root@hissam.office.simonwunderlich.net>
Hi root,
kernel test robot noticed the following build warnings:
[auto build test WARNING on wireless-next/main]
[also build test WARNING on wireless/main linus/master v6.11-rc3 next-20240812]
[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/root/cfg80211-Set-the-channel-definition-for-the-different-Wi-Fi-modes-when-starting-CAC/20240812-202257
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link: https://lore.kernel.org/r/20240812120909.2721400-1-root%40hissam.office.simonwunderlich.net
patch subject: [PATCH] cfg80211: Set the channel definition for the different Wi-Fi modes when starting CAC
config: i386-buildonly-randconfig-005-20240813 (https://download.01.org/0day-ci/archive/20240813/202408130337.tnSP4Qys-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240813/202408130337.tnSP4Qys-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/202408130337.tnSP4Qys-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/wireless/nl80211.c:10146:11: warning: 9 enumeration values not handled in switch: 'NL80211_IFTYPE_UNSPECIFIED', 'NL80211_IFTYPE_STATION', 'NL80211_IFTYPE_AP_VLAN'... [-Wswitch]
10146 | switch (wdev->iftype) {
| ^~~~~~~~~~~~
1 warning generated.
vim +10146 net/wireless/nl80211.c
10068
10069 static int nl80211_start_radar_detection(struct sk_buff *skb,
10070 struct genl_info *info)
10071 {
10072 struct cfg80211_registered_device *rdev = info->user_ptr[0];
10073 struct net_device *dev = info->user_ptr[1];
10074 struct wireless_dev *wdev = dev->ieee80211_ptr;
10075 struct wiphy *wiphy = wdev->wiphy;
10076 struct cfg80211_chan_def chandef;
10077 enum nl80211_dfs_regions dfs_region;
10078 unsigned int cac_time_ms;
10079 int err = -EINVAL;
10080
10081 flush_delayed_work(&rdev->dfs_update_channels_wk);
10082
10083 switch (wdev->iftype) {
10084 case NL80211_IFTYPE_AP:
10085 case NL80211_IFTYPE_P2P_GO:
10086 case NL80211_IFTYPE_MESH_POINT:
10087 case NL80211_IFTYPE_ADHOC:
10088 break;
10089 default:
10090 /* caution - see cfg80211_beaconing_iface_active() below */
10091 return -EINVAL;
10092 }
10093
10094 wiphy_lock(wiphy);
10095
10096 dfs_region = reg_get_dfs_region(wiphy);
10097 if (dfs_region == NL80211_DFS_UNSET)
10098 goto unlock;
10099
10100 err = nl80211_parse_chandef(rdev, info, &chandef);
10101 if (err)
10102 goto unlock;
10103
10104 err = cfg80211_chandef_dfs_required(wiphy, &chandef, wdev->iftype);
10105 if (err < 0)
10106 goto unlock;
10107
10108 if (err == 0) {
10109 err = -EINVAL;
10110 goto unlock;
10111 }
10112
10113 if (!cfg80211_chandef_dfs_usable(wiphy, &chandef)) {
10114 err = -EINVAL;
10115 goto unlock;
10116 }
10117
10118 if (nla_get_flag(info->attrs[NL80211_ATTR_RADAR_BACKGROUND])) {
10119 err = cfg80211_start_background_radar_detection(rdev, wdev,
10120 &chandef);
10121 goto unlock;
10122 }
10123
10124 if (cfg80211_beaconing_iface_active(wdev) || wdev->cac_started) {
10125 err = -EBUSY;
10126 goto unlock;
10127 }
10128
10129 /* CAC start is offloaded to HW and can't be started manually */
10130 if (wiphy_ext_feature_isset(wiphy, NL80211_EXT_FEATURE_DFS_OFFLOAD)) {
10131 err = -EOPNOTSUPP;
10132 goto unlock;
10133 }
10134
10135 if (!rdev->ops->start_radar_detection) {
10136 err = -EOPNOTSUPP;
10137 goto unlock;
10138 }
10139
10140 cac_time_ms = cfg80211_chandef_dfs_cac_time(&rdev->wiphy, &chandef);
10141 if (WARN_ON(!cac_time_ms))
10142 cac_time_ms = IEEE80211_DFS_MIN_CAC_TIME_MS;
10143
10144 err = rdev_start_radar_detection(rdev, dev, &chandef, cac_time_ms);
10145 if (!err) {
10146 switch (wdev->iftype) {
10147 case NL80211_IFTYPE_MESH_POINT:
10148 wdev->u.mesh.chandef = chandef;
10149 break;
10150 case NL80211_IFTYPE_ADHOC:
10151 wdev->u.ibss.chandef = chandef;
10152 break;
10153 case NL80211_IFTYPE_OCB:
10154 wdev->u.ocb.chandef = chandef;
10155 break;
10156 case NL80211_IFTYPE_AP:
10157 case NL80211_IFTYPE_P2P_GO:
10158 wdev->links[0].ap.chandef = chandef;
10159 break;
10160 }
10161 wdev->cac_started = true;
10162 wdev->cac_start_time = jiffies;
10163 wdev->cac_time_ms = cac_time_ms;
10164 }
10165 unlock:
10166 wiphy_unlock(wiphy);
10167
10168 return err;
10169 }
10170
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-12 20:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 12:09 [PATCH] cfg80211: Set the channel definition for the different Wi-Fi modes when starting CAC root
2024-08-12 17:49 ` kernel test robot
2024-08-12 20:14 ` kernel test robot [this message]
2024-08-13 11:12 ` Issam Hamdi
2024-08-15 6:35 ` Kalle Valo
2024-08-15 7:54 ` [PATCH] wifi: " Issam Hamdi
2024-08-15 8:53 ` Kalle Valo
2024-08-15 11:32 ` [PATCH v2] " Issam Hamdi
2024-08-15 17:42 ` Jeff Johnson
2024-08-16 14:24 ` [PATCH v3] " Issam Hamdi
2024-08-23 10:42 ` Johannes Berg
2024-08-26 9:51 ` Hamdi Issam
2024-08-29 9:09 ` [PATCH v4] " Issam Hamdi
-- strict thread matches above, loose matches on Subject: below --
2024-08-12 12:41 [PATCH] " Issam Hamdi
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=202408130337.tnSP4Qys-lkp@intel.com \
--to=lkp@intel.com \
--cc=ih@simonwunderlich.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mathias.kretschmer@fit.fraunhofer.de \
--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.