On Wed, 2017-10-25 at 14:50 +0530, Vidyullatha Kanchanapally wrote: > + * @UPDATE_FILS_ERP_INFO: Indicates that FILS connection parameters (realm, > + * username, erp sequence number and rrk) are updated > + * @UPDATE_AUTH_TYPE: Indicates that Authentication type is updated These are new here, but you don't know if they were actually supported: > + if (wiphy_ext_feature_isset(&rdev->wiphy, > + NL80211_EXT_FEATURE_FILS_SK_OFFLOAD) && here. > + info->attrs[NL80211_ATTR_FILS_ERP_USERNAME] && > + info->attrs[NL80211_ATTR_FILS_ERP_REALM] && > + info->attrs[NL80211_ATTR_FILS_ERP_NEXT_SEQ_NUM] && > + info->attrs[NL80211_ATTR_FILS_ERP_RRK]) { [...] > + } else if (info->attrs[NL80211_ATTR_FILS_ERP_USERNAME] || > + info->attrs[NL80211_ATTR_FILS_ERP_REALM] || > + info->attrs[NL80211_ATTR_FILS_ERP_NEXT_SEQ_NUM] || > + info->attrs[NL80211_ATTR_FILS_ERP_RRK]) { > + return -EINVAL; > + } This logic is also really odd, why not if (attrs) { if (not flag) return -EINVAL; /* use attrs etc. */ } > + > + if (info->attrs[NL80211_ATTR_AUTH_TYPE]) { > + u32 auth_type = > + nla_get_u32(info->attrs[NL80211_ATTR_AUTH_TYPE]); > + if (!nl80211_valid_auth_type(rdev, auth_type, > + NL80211_CMD_CONNECT)) > + return -EINVAL; > + connect.auth_type = auth_type; > + changed |= UPDATE_AUTH_TYPE; > + } Again, how do you know the driver will actually look at UPDATE_AUTH_TYPE? johannes