linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [RFC PATCH 1/2] wifi: wireless: warn on most wireless extension usage
Date: Thu, 17 Nov 2022 12:48:24 +0200	[thread overview]
Message-ID: <87v8ndrh53.fsf@kernel.org> (raw)
In-Reply-To: <20221104174218.26f9541c0bfa.Ifcf30eeeb8fc7019e4dcf2782b04515254d165e1@changeid> (Johannes Berg's message of "Fri, 4 Nov 2022 17:42:20 +0100")

Johannes Berg <johannes@sipsolutions.net> writes:

> From: Johannes Berg <johannes.berg@intel.com>
>
> With MLO/EHT support around the corner, we're going to
> remove support for wireless extensions with new devices
> since MLO cannot be properly indicated using them.
>
> Add a warning to indicate which processes are still
> using wireless extensions, if being used with modern
> (i.e. cfg80211) drivers.

I doubt people outside of wireless know what MLO or EHT are :) Also it
would be good to mention what's the replacement for wireless extensions
so better to spell out that as well. So maybe use more widely known
terminology like this:

"With Wi-Fi 7 (IEEE 802.11be) support around the corner, we're going to
remove support for wireless extensions with new devices since Multi-Link
Operation (MLO) feature cannot be properly indicated using them.

Add a warning to indicate which processes are still using the ancient
wireless extensions, if being used with modern (i.e. cfg80211) drivers.
All those users should be using nl80211 instead.

Ancient drivers, which are not using cfg80211, are unaffected."

> +#ifdef CONFIG_CFG80211_WEXT
> +static void wireless_warn_cfg80211_wext(void)
> +{
> +	char name[sizeof(current->comm)];
>  
> +	pr_warn_ratelimited("warning: `%s' uses wireless extensions that are deprecated for modern drivers\n",
> +			    get_task_comm(name, current));
> +}
> +#endif

Maybe add ", switch to nl80211" also to the warning message?

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  parent reply	other threads:[~2022-11-17 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 16:42 [RFC PATCH 1/2] wifi: wireless: warn on most wireless extension usage Johannes Berg
2022-11-04 16:42 ` [RFC PATCH 2/2] wifi: wireless: deny wireless extensions on MLO-capable devices Johannes Berg
2022-11-17 10:51   ` Kalle Valo
2022-11-17 10:58     ` Johannes Berg
2022-11-17 11:05       ` Kalle Valo
2022-11-17 10:48 ` Kalle Valo [this message]
2022-11-17 10:49   ` [RFC PATCH 1/2] wifi: wireless: warn on most wireless extension usage 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=87v8ndrh53.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).