From: Johannes Berg <johannes@sipsolutions.net>
To: Aditya Kumar Singh <quic_adisi@quicinc.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: cfg80211: fix WARN_ON during CAC cancelling
Date: Wed, 20 Nov 2024 09:59:38 +0100 [thread overview]
Message-ID: <b28eb973d42b680db268eda1868b672264ab12be.camel@sipsolutions.net> (raw)
In-Reply-To: <a074905b-34c5-4cc3-a38f-a2c4bc281e5d@quicinc.com>
On Tue, 2024-11-19 at 11:23 +0530, Aditya Kumar Singh wrote:
>
> --- a/net/mac80211/cfg.c
> +++ b/net/mac80211/cfg.c
> @@ -5046,10 +5046,11 @@ static void ieee80211_del_intf_link(struct wiphy
> *wiphy,
> unsigned int link_id)
> {
> struct ieee80211_sub_if_data *sdata =
> IEEE80211_WDEV_TO_SUB_IF(wdev);
> + u16 new_links = wdev->valid_links & ~BIT(link_id);
>
> lockdep_assert_wiphy(sdata->local->hw.wiphy);
>
> - ieee80211_vif_set_links(sdata, wdev->valid_links, 0);
> + ieee80211_vif_set_links(sdata, new_links, 0);
> }
Needing this part is sort of clear then, but maybe not entirely obvious?
Should probably be accompanied by some documentation updates.
> So I will submit this as patch then?
Seems reasonable.
> > There's necessarily going to be some temporary inconsistency here, I'm
> > not sure it matters too much if it isn't very visible?
> >
>
> Any particular case you suspect and want me to test?
No, not really.
> I'm more inclining towards the first suggestion you gave - clearing the
> bitmap later. What's your suggestion?
>
Sure.
johannes
prev parent reply other threads:[~2024-11-20 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 6:27 [PATCH] wifi: cfg80211: fix WARN_ON during CAC cancelling Aditya Kumar Singh
2024-11-13 9:29 ` Johannes Berg
2024-11-13 14:43 ` Aditya Kumar Singh
2024-11-13 15:48 ` Johannes Berg
2024-11-13 16:20 ` Aditya Kumar Singh
2024-11-15 8:14 ` Johannes Berg
2024-11-19 5:53 ` Aditya Kumar Singh
2024-11-20 8:59 ` Johannes Berg [this message]
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=b28eb973d42b680db268eda1868b672264ab12be.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@quicinc.com \
/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