From: Aloka Dixit <alokad@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH v4 1/2] nl80211: Add FILS discovery support
Date: Thu, 30 Jul 2020 14:17:46 -0700 [thread overview]
Message-ID: <2b1ea1c4baedcb119f4e632b26399071@codeaurora.org> (raw)
In-Reply-To: <c3dbcc3e4ee2d3596625e8c1226325180444a961.camel@sipsolutions.net>
On 2020-07-30 07:43, Johannes Berg wrote:
> On Wed, 2020-06-17 at 22:04 -0700, Aloka Dixit wrote:
>> + * @NL80211_FILS_DISCOVERY_TMPL: Optional FILS discovery template.
>> + * It has contents of IEEE Std 802.11ai-2016 9.6.8.36 FILS discovery
>> frame
>> + * (Figure 9-687a).
>
> Is that
>
> "It has (contents of ... FILS discovery frame) ..."
>
> or
>
> "It has contents of (... FILS discovery frame) ..."?
>
> I mean, is that with or without headers? The wording doesn't seem
> entirely clear to me.
>
> OTOH, if it's with headers, how could it be optional? In fact, either
> way, how is it optional?
>
Template has management frame headers as well. Will change the wording
accordingly.
I made the template optional because FILS discovery may or may not be
offloaded to FW.
Another way would be to make it mandatory here.
>> +static int nl80211_parse_fils_discovery(struct nlattr *attrs,
>> + struct cfg80211_ap_settings *params)
>> +{
>> + struct nlattr *tmpl;
>> + struct nlattr *tb[NL80211_FILS_DISCOVERY_MAX + 1];
>> + int ret;
>> + struct cfg80211_fils_discovery *fd = ¶ms->fils_discovery;
>> +
>> + ret = nla_parse_nested(tb, NL80211_FILS_DISCOVERY_MAX, attrs,
>> + fils_discovery_policy, NULL);
>> + if (ret)
>> + return ret;
>> +
>> + if (!tb[NL80211_FILS_DISCOVERY_INT_MIN] ||
>> + !tb[NL80211_FILS_DISCOVERY_INT_MAX])
>> + return -EINVAL;
>> +
>> + fd->min_interval = nla_get_u32(tb[NL80211_FILS_DISCOVERY_INT_MIN]);
>> + fd->max_interval = nla_get_u32(tb[NL80211_FILS_DISCOVERY_INT_MAX]);
>> +
>> + tmpl = tb[NL80211_FILS_DISCOVERY_TMPL];
>> + if (tmpl) {
>> + fd->tmpl = nla_data(tmpl);
>> + fd->tmpl_len = nla_len(tmpl);
>
> And if it's with headers, it should have some kind of minimum length
> too? You've only put a maximum length into the policy.
>
> (Which reminds me I wanted to have an NLA_POLICY_RANGE(NLA_BINARY, min,
> max) but haven't done that yet ...)
>
Yeah, I looked through existing examples for NLA_BINARY, those provide
only the higher bound for length.
But I can modify it to range once that is added.
> johannes
next prev parent reply other threads:[~2020-07-30 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 5:04 [PATCH v4 0/2] Add FILS discovery support Aloka Dixit
2020-06-18 5:04 ` [PATCH v4 1/2] nl80211: " Aloka Dixit
2020-07-30 14:43 ` Johannes Berg
2020-07-30 21:17 ` Aloka Dixit [this message]
2020-07-30 21:22 ` Johannes Berg
2020-07-30 21:53 ` Aloka Dixit
2020-06-18 5:04 ` [PATCH v4 2/2] mac80211: " Aloka Dixit
2020-07-30 14:47 ` Johannes Berg
2020-07-30 21:00 ` Aloka Dixit
2020-07-30 21:26 ` Johannes Berg
2020-07-30 22:08 ` Aloka Dixit
2020-07-31 8:21 ` Johannes Berg
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=2b1ea1c4baedcb119f4e632b26399071@codeaurora.org \
--to=alokad@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).