From: Kalle Valo <kvalo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
bpf@vger.kernel.org, ast@kernel.org
Subject: Re: [PULL] Networking for v6.3
Date: Thu, 23 Feb 2023 21:06:00 +0200 [thread overview]
Message-ID: <87pma02odj.fsf@kernel.org> (raw)
In-Reply-To: <CAHk-=wjTMgB0=PQt8synf1MRTfetVXAWWLOibnMKvv1ETn_1uw@mail.gmail.com> (Linus Torvalds's message of "Thu, 23 Feb 2023 09:21:38 -0800")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Tue, Feb 21, 2023 at 3:38 PM Jakub Kicinski <kuba@kernel.org> wrote:
> --
>> Networking changes for 6.3.
>
> Hmm. I just noticed another issue on my laptop: I get an absolute *flood* of
>
> warning: 'ThreadPoolForeg' uses wireless extensions that are
> deprecated for modern drivers: use nl80211
>
> introduced in commit dc09766c755c ("wifi: wireless: warn on most
> wireless extension usage").
>
> This is on my xps13 with Atheros QCA6174 wireless ("Killer 1435
> Wireless-AC", PCI ID 168c:003e, subsystem 1a56:143a).
>
> And yes, it uses 'pr_warn_ratelimited()', but the ratelimiting is a
> joke. That means that I "only" get five warnings a second, and then it
> pauses for a minute or two until it does it again.
>
> So that warning needs to go away - it flushed the whole kernel printk
> buffer in no time.
Ouch, sorry about that. The ratelimiting is really a joke here. We'll
send a patch tomorrow.
So that we can file a bug report about use of Wireless Extensions, what
process is ThreadPoolForeg? I did a quick search and it seems to be
Chromium related, but is it really from Chromium? The warning was
applied over a month ago, I'm surprised nobody else has reported
anything. I would expect that there are more Chromium users :)
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-02-23 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 23:38 [PULL] Networking for v6.3 Jakub Kicinski
2023-02-22 2:46 ` Linus Torvalds
2023-02-22 3:33 ` Jakub Kicinski
2023-02-22 19:07 ` Alexander Lobakin
2023-02-22 2:50 ` pr-tracker-bot
2023-02-23 17:21 ` Linus Torvalds
2023-02-23 19:06 ` Kalle Valo [this message]
2023-02-23 21:37 ` Linus Torvalds
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=87pma02odj.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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).