All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Kalle Valo <kvalo@kernel.org>,
	"Berg, Johannes" <johannes.berg@intel.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	Nicolas Cavallari <Nicolas.Cavallari@green-communications.fr>,
	Johannes Berg <johannes.berg@intel.com>,
	Jan Engelhardt <jengelh@inai.de>
Subject: Re: [PATCH] wifi: wext: warn about usage only once
Date: Sat, 25 Feb 2023 20:09:51 -0600	[thread overview]
Message-ID: <121c0039-5f0c-7c4e-5b07-9193ed547079@lwfinger.net> (raw)
In-Reply-To: <CAHk-=whwDRefJJq0K8bXXSNY3-Zy8=Z3ZiKYh2mOOvfT-MqNhA@mail.gmail.com>

On 2/24/23 13:44, Linus Torvalds wrote:
> You *could* improve on it further by having some kind of timed
> rate-limiting, where every 24 hours you'd clear the warning mask, so
> that you'd warn about these things once a day. That *can* be useful
> for when people just don't notice the warning the first time around,
> and "once a day" is not a horribly problem that fills up the logs like
> the current situation does.
> 
> But again - I personally think even just a pr_warn_once() is likely
> good enough. Because all I want is to not have that horrible
> log-flushing behavior.

To all,

I posted my list of 8 different tasks that generated this warning to the 
openSUSE developers mailing list, and got back a reply from Jan Engelhardt 
pointed me toward the libqt5-qtbase project, which contains the following snippet:

     case ARPHRD_ETHER:
         // check if it's a WiFi interface
         if (qt_safe_ioctl(socket, SIOCGIWMODE, req) >= 0)
             return QNetworkInterface::Wifi;
         return QNetworkInterface::Ethernet;

I am not entirely sure why Qt needs to know what type of device the network is 
using. I tested by replacing this with

     case ARPHRD_ETHER:
         return QNetworkInterface::Ethernet;


After rebuilding the entire project, and reinstalling all 31 packages generated 
in a new build, my system now displays only 3 remaining warnings, namely

warning: `nspr-2' uses wireless extensions that are deprecated for modern 
drivers; use nl80211
warning: `ThreadPoolForeg' uses wireless extensions that are deprecated for 
modern drivers; use nl80211
warning: `nspr-8' uses wireless extensions that are deprecated for modern 
drivers; use nl80211

To answer Kalle's question, libQt is responsible for most of the warnings that 
were reported here.

In case Qt really needs to know what network it is on, what is a better way to 
detect if the network is on a Wifi device?

Larry




  reply	other threads:[~2023-02-26  2:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 12:59 [PATCH] wifi: wext: warn about usage only once Johannes Berg
2023-02-24 15:03 ` Kalle Valo
2023-02-24 19:47   ` Jakub Kicinski
2023-02-25  4:54     ` Kalle Valo
2023-02-24 15:45 ` Larry Finger
2023-02-24 19:44   ` Linus Torvalds
2023-02-26  2:09     ` Larry Finger [this message]
2023-02-27 18:32       ` Jakub Kicinski
2023-02-26 17:36 ` Kalle Valo
2023-02-26 17:40   ` Kalle Valo
2023-02-26 17:54 ` Kalle Valo

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=121c0039-5f0c-7c4e-5b07-9193ed547079@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Nicolas.Cavallari@green-communications.fr \
    --cc=jengelh@inai.de \
    --cc=johannes.berg@intel.com \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.