public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Léo Lam" <leo@leolam.fr>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] wifi: nl80211: fix deadlock in nl80211_set_cqm_rssi (6.6.x)
Date: Mon, 11 Dec 2023 13:45:21 +0100	[thread overview]
Message-ID: <2023121147-estrogen-reviver-afb4@gregkh> (raw)
In-Reply-To: <2023121135-unwilling-exception-0bcc@gregkh>

On Mon, Dec 11, 2023 at 07:47:32AM +0100, Greg KH wrote:
> On Sun, Dec 10, 2023 at 09:39:30PM +0000, Léo Lam wrote:
> > Commit 4a7e92551618f3737b305f62451353ee05662f57 ("wifi: cfg80211: fix
> > CQM for non-range use" on 6.6.x) causes nl80211_set_cqm_rssi not to
> > release the wdev lock in some situations.
> > 
> > Of course, the ensuing deadlock causes userland network managers to
> > break pretty badly, and on typical systems this also causes lockups on
> > on suspend, poweroff and reboot. See [1], [2], [3] for example reports.
> > 
> > The upstream commit, 7e7efdda6adb385fbdfd6f819d76bc68c923c394
> > ("wifi: cfg80211: fix CQM for non-range use"), does not trigger this
> > issue because the wdev lock does not exist there.
> > 
> > Fix the deadlock by releasing the lock before returning.
> > 
> > [1] https://bugzilla.kernel.org/show_bug.cgi?id=218247
> > [2] https://bbs.archlinux.org/viewtopic.php?id=290976
> > [3] https://lore.kernel.org/all/87sf4belmm.fsf@turtle.gmx.de/
> > 
> > Fixes: 4a7e92551618 ("wifi: cfg80211: fix CQM for non-range use")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Léo Lam <leo@leolam.fr>
> > ---
> >  net/wireless/nl80211.c | 18 ++++++++++++------
> >  1 file changed, 12 insertions(+), 6 deletions(-)
> 
> So this is only for the 6.6.y tree?  If so, you should at least cc: the
> other wireless developers involved in the original fix, right?
> 
> And what commit actually fixed this issue upstream, why not take that
> instead?

I've reverted the offending commit in the last 6.1.y and 6.6.y release,
so can you send this as a patch series, first one being the original
backport, and the second one this one, AFTER it has been tested?

thanks,

greg k-h

  reply	other threads:[~2023-12-11 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 21:39 [PATCH] wifi: nl80211: fix deadlock in nl80211_set_cqm_rssi (6.6.x) Léo Lam
2023-12-11  6:47 ` Greg KH
2023-12-11 12:45   ` Greg KH [this message]
2023-12-11 23:07     ` Léo Lam
2023-12-11 22:57   ` Léo Lam
2023-12-11 23:15     ` Philip Müller
2023-12-11 23:59       ` Léo Lam
2023-12-11 22:41 ` Philip Müller
2023-12-12 16:07 ` Arnab Bose
  -- strict thread matches above, loose matches on Subject: below --
2023-12-12 15:54 Arnab Bose

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=2023121147-estrogen-reviver-afb4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=leo@leolam.fr \
    --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