From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: Johannes Berg <johannes.berg@intel.com>, stable@vger.kernel.org
Subject: Re: [Regression] 6.1.66, 6.6.5 - wifi: cfg80211: fix CQM for non-range use
Date: Mon, 11 Dec 2023 10:40:39 +0100 [thread overview]
Message-ID: <2023121128-unlighted-bagful-f6f1@gregkh> (raw)
In-Reply-To: <2023121127-obstinate-constable-e04f@gregkh>
On Mon, Dec 11, 2023 at 10:39:26AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Dec 11, 2023 at 04:26:26PM +0700, Philip Müller wrote:
> > On 11.12.23 16:25, Greg Kroah-Hartman wrote:
> > > On Mon, Dec 11, 2023 at 04:02:11PM +0700, Philip Müller wrote:
> > > > Hi Johannes, hi Greg,
> > > >
> > > > Any tree that back-ported 7e7efdda6adb wifi: cfg80211: fix CQM for non-range
> > > > use that does not contain 076fc8775daf wifi: cfg80211: remove wdev mutex
> > > > (which does not apply cleanly to 6.6.y or 6.6.1) will be affected.
> > > >
> > > > You can find a downstream bug report at Arch Linux:
> > > >
> > > > https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/17
> > > >
> > > > So we should either revert 7e7efdda6adb or backport the needed to those
> > > > kernel series. 6.7.y is reported to work with 6.7.0-rc4.
> > >
> > > Yeah, this looks bad, I'll go just revert this for now and push out a
> > > new release with the fix as lots of people are hitting it.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> >
> > Hi Greg,
> >
> > there is actually a fix for it:
> >
> > https://www.spinics.net/lists/stable/msg703040.html
>
> That "fix" was not cc:ed to any of the wifi developers and would need a
> lot of review before I feel comfortable accepting it, as I said in the
> response to that message.
>
> Also, please point to lore.kernel.org lists, it's much easier to handle
> as we don't have any control over any other archive web site.
Also, have you tested that proposed fix?
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-11 9:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 9:02 [Regression] 6.1.66, 6.6.5 - wifi: cfg80211: fix CQM for non-range use Philip Müller
2023-12-11 9:25 ` Greg Kroah-Hartman
2023-12-11 9:26 ` Philip Müller
2023-12-11 9:39 ` Greg Kroah-Hartman
2023-12-11 9:40 ` Greg Kroah-Hartman [this message]
2023-12-11 9:46 ` Philip Müller
2023-12-11 10:17 ` Philip Müller
2023-12-11 11:50 ` Greg Kroah-Hartman
2023-12-11 20:58 ` Berg, Johannes
2023-12-11 22:26 ` Philip Müller
2023-12-13 23:38 ` Philip Müller
2023-12-14 8:05 ` Berg, Johannes
2023-12-14 8:18 ` Greg Kroah-Hartman
2023-12-14 8:24 ` Berg, Johannes
2023-12-14 8:32 ` Philip Müller
2023-12-14 11:59 ` Greg Kroah-Hartman
2023-12-16 10:47 ` Philip Müller
2023-12-16 17:58 ` Léo Lam
2024-01-03 3:45 ` Philip Müller
2024-01-03 10:09 ` Greg Kroah-Hartman
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=2023121128-unlighted-bagful-f6f1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=philm@manjaro.org \
--cc=stable@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