From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Mikhail Karpenko <mkarpenko@quantenna.com>
Subject: Re: [RFC PATCH] cfg80211: fix duplicated scan entries after channel switch
Date: Tue, 02 Jul 2019 14:40:57 +0200 [thread overview]
Message-ID: <b2aa2ee9af4cf4cd2c29139122044fcfae077079.camel@sipsolutions.net> (raw)
In-Reply-To: <20190702115005.ulcfohbi4mkwpt2c@bars>
Hi Sergey,
On Tue, 2019-07-02 at 11:50 +0000, Sergey Matyukevich wrote:
> Thanks for review! Summarizing your comments, here are the options
> and some of their highlights:
>
> 1. replace old entry with the new entry
> - no easy way to update ifmgd->associated w/o rework of mac80211 csa
Yes, this one's the tricky one. I don't think you can make this work
easily.
> 2. keep old entry, remove new entry
> - this is what suggested RFC patch does
> - works, but update of current_bss entry after csa may be delayed
Correct.
> 3. keep old entry, update it using data from new entry, then remove new entry
> - this looks like a better approach
>
> Unless I am missing something, the last option can be implemented on top of
> the current RFC patch w/o extra complexity. The required bss entry update is
> what cfg80211_bss_update function does when bss in question already exists.
> So it should be possible to reuse that code.
Agree, you just need to sort of invert it, or call it like this:
* relink the old entry, unlink a new entry (if any)
* bss_update() with the new entry if there was one
* it should free one of the entries if I remember correctly
> I will post RFC patch v2 after more testing for both mac80211 and
> fullmac cases.
Sounds good, thanks a lot for working on this!
johannes
prev parent reply other threads:[~2019-07-02 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 11:21 [RFC PATCH] cfg80211: fix duplicated scan entries after channel switch Sergey Matyukevich
2019-06-28 14:39 ` Johannes Berg
2019-07-02 11:50 ` Sergey Matyukevich
2019-07-02 12:40 ` 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=b2aa2ee9af4cf4cd2c29139122044fcfae077079.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mkarpenko@quantenna.com \
--cc=sergey.matyukevich.os@quantenna.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