From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W . Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>
Subject: Re: [PATCH v1] cfg80211: Support for 4-way handshake offloading for WPA2-Personal
Date: Thu, 23 Aug 2012 18:54:20 +0300 [thread overview]
Message-ID: <1850661.W9RYC5ddVW@lx-vladimir> (raw)
In-Reply-To: <1345461629.4459.10.camel@jlt3.sipsolutions.net>
On Monday, August 20, 2012 01:20:29 PM Johannes Berg wrote:
> On Thu, 2012-08-02 at 14:33 +0300, Vladimir Kondratiev wrote:
> > + * @NL80211_ATTR_4WAY_HANDSHAKE_OFFLOAD_STA: This is a flag that
> > indicates to + * WPA supplicant that 4-way handshake has been offloaded
> > to the firmware + * in the STA mode.
> > + * In this case, WPA supplicant will provide driver with PSK for
> > + * connect()
> > + *
> > + * @NL80211_ATTR_4WAY_HANDSHAKE_OFFLOAD_AP: This is a flag that indicates
> > to + * WPA supplicant that 4-way handshake has been offloaded to the
> > firmware + * in the AP mode.
> > + * In this case, WPA supplicant will provide driver with PSK for
> > + * start_ap()
>
> I think you should use the nl80211 driver flags, not extra attributes
> here.
I thought I need to use same approach as for other flags. All other use bit in
wiphy.flags and NL80211_ATTR_xxx. And reason is simple - in the NL80211, it is
enum, while for the driver one need to reserve a bit. This is how other flags
are dealt with:
if ((dev->wiphy.flags & WIPHY_FLAG_IBSS_RSN) &&
nla_put_flag(msg, NL80211_ATTR_SUPPORT_IBSS_RSN))
goto nla_put_failure;
if ((dev->wiphy.flags & WIPHY_FLAG_MESH_AUTH) &&
nla_put_flag(msg, NL80211_ATTR_SUPPORT_MESH_AUTH))
goto nla_put_failure;
if ((dev->wiphy.flags & WIPHY_FLAG_AP_UAPSD) &&
nla_put_flag(msg, NL80211_ATTR_SUPPORT_AP_UAPSD))
goto nla_put_failure;
if ((dev->wiphy.flags & WIPHY_FLAG_SUPPORTS_FW_ROAM) &&
nla_put_flag(msg, NL80211_ATTR_ROAM_SUPPORT))
goto nla_put_failure;
if ((dev->wiphy.flags & WIPHY_FLAG_SUPPORTS_TDLS) &&
nla_put_flag(msg, NL80211_ATTR_TDLS_SUPPORT))
goto nla_put_failure;
if ((dev->wiphy.flags & WIPHY_FLAG_TDLS_EXTERNAL_SETUP) &&
nla_put_flag(msg, NL80211_ATTR_TDLS_EXTERNAL_SETUP))
goto nla_put_failure;
if ((dev->wiphy.flags & WIPHY_FLAG_4WAY_HANDSHAKE_OFFLOAD_STA) &&
nla_put_flag(msg, NL80211_ATTR_4WAY_HANDSHAKE_OFFLOAD_STA))
goto nla_put_failure;
>
> And the descriptions (and flag checking!) should make it clear that it
> is only supported with the connect() API, not with the auth/assoc APIs.
>
> > + * @WIPHY_FLAG_4WAY_HANDSHAKE_OFFLOAD: Device supports 4-way handshake
> > offload.
> Use nl80211 flag directly. Also, docs are wrong:
> > + WIPHY_FLAG_4WAY_HANDSHAKE_OFFLOAD_STA = BIT(22),
> > + WIPHY_FLAG_4WAY_HANDSHAKE_OFFLOAD_AP = BIT(23),
>
> Please also add validation that these flags are specified only when the
> correct APIs (connect/start_ap) are supported.
Agree, will add both doc and validation.
I want to do some more work exploring how this offload serves in real life,
will submit when (if?) it will be ready.
Thanks, Vladimir.
next prev parent reply other threads:[~2012-08-23 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 11:33 [PATCH v1] 4-way handshake offloading Vladimir Kondratiev
2012-08-02 11:33 ` [PATCH v1] cfg80211: Support for 4-way handshake offloading for WPA2-Personal Vladimir Kondratiev
2012-08-20 11:20 ` Johannes Berg
2012-08-23 15:54 ` Vladimir Kondratiev [this message]
2012-08-23 15:59 ` Johannes Berg
[not found] ` <3373913.UaOl7A5Fl4@lx-vladimir>
2012-08-26 7:44 ` Johannes Berg
2012-08-27 15:26 ` Scalable approach for nl80211_feature_flags Vladimir Kondratiev
2012-08-28 9:16 ` Kalle Valo
2012-08-27 15:32 ` Vladimir Kondratiev
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=1850661.W9RYC5ddVW@lx-vladimir \
--to=qca_vkondrat@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rodrigue@qca.qualcomm.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