From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 1/2] station: skip disabled frequencies in neighbor report
Date: Mon, 10 Oct 2022 12:40:10 -0700 [thread overview]
Message-ID: <20221010194011.55962-1-prestwoj@gmail.com> (raw)
Use the disabled frequency list to check if the neighbor report is
including a frequency which IWD cannot use.
---
src/station.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/station.c b/src/station.c
index 19cba680..f138846d 100644
--- a/src/station.c
+++ b/src/station.c
@@ -1813,6 +1813,8 @@ static void parse_neighbor_report(struct station *station,
struct handshake_state *hs = netdev_get_handshake(station->netdev);
const struct scan_freq_set *supported =
wiphy_get_supported_freqs(station->wiphy);
+ const struct scan_freq_set *disabled =
+ wiphy_get_disabled_freqs(station->wiphy);
freq_set_md = scan_freq_set_new();
freq_set_no_md = scan_freq_set_new();
@@ -1849,8 +1851,9 @@ static void parse_neighbor_report(struct station *station,
if (!(band & wiphy_get_supported_bands(station->wiphy)))
continue;
- /* Skip if frequency is not supported */
- if (!scan_freq_set_contains(supported, freq))
+ /* Skip if frequency is not supported or disabled */
+ if (!scan_freq_set_contains(supported, freq) ||
+ scan_freq_set_contains(disabled, freq))
continue;
if (!memcmp(info.addr,
--
2.34.3
next reply other threads:[~2022-10-10 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 19:40 James Prestwood [this message]
2022-10-10 19:40 ` [PATCH 2/2] station: contrain known frequencies before roam scan James Prestwood
2022-10-11 19:31 ` [PATCH 1/2] station: skip disabled frequencies in neighbor report Denis Kenzior
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=20221010194011.55962-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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