On Thu, 2020-07-30 at 14:00 -0700, Aloka Dixit wrote:
> > > + fd = &sdata->vif.bss_conf.fils_discovery;
> > > + fd->min_interval = params->min_interval;
> > > + fd->max_interval = params->max_interval;
> > > +
> > > + if (!params->tmpl || !params->tmpl_len) /* Optional template */
> > > + return 0;
> >
> > Now I'm even more confused. If the template is optional, then if it's
> > not given it doesn't mean *everything* should be ignored, does it?
> >
> > What would be the point of that? OTOH, if the template isn't there,
> > what
> > would you do?
> >
> > But it still doesn't make sense - if no template means you shouldn't do
> > anything then that doesn't mean the template should be optional, that
> > just means userspace shouldn't even put the NL80211_ATTR_FILS_DISCOVERY
> > attribute when it doesn't want anything to be done?
> >
> > So it seems to me that something doesn't match. Either the template is
> > truly optional and then this shouldn't just return success, or the
> > template isn't actually optional?
> >
>
> Everything is not ignored, I set the minimum and maximum interval values
> before checking for the template so that those are accepted even if
> template isn't present.
Right, oops, missed that.
> For 6GHz, template is required, at least for ath11k driver.
> But for 2.4GHz and 5GHz FILS discovery transmission is not offloaded to
> FW.
But ... now I'm still confused.
If you *don't* offload it, how will it work? Will it all bubble up to
hostapd and that will send the response? Does that work without any
other changes?
But then what would you need the min/max for? I guess I still don't
understand it... I thought this was a periodic frame anyway like beacon,
so how could you _not_ offload it?
> We can make the template mandatory instead and then the respective
> drivers will choose the handling.
> Please suggest.
I have no idea ... still trying to understand it.
> > > + err = ieee80211_set_fils_discovery(sdata, ¶ms->fils_discovery);
> > > + if (err < 0) {
> > > + ieee80211_vif_release_channel(sdata);
> > > + return err;
> >
> > Is there no goto label for this error case?
> >
>
> Existing function doesn't use goto labels for error cases, only return.
Maybe add one? Surely the release_channel() must alraedy exist there
somewhere.
> > > + skb = dev_alloc_skb(tmpl->len);
> > > + if (skb)
> > > + skb_put_data(skb, tmpl->data, tmpl->len);
> >
> > You should consider the headroom that the driver may have requested.
> >
>
> I didn't understand this point, what would the driver request headroom
> for?
Whatever it wants for ... drivers are allowed request extra headroom
(hw->extra_tx_headroom) and we generally honour that for every skb we
build for the driver.
johannes
