From: Simon Horman <simon.horman@corigine.com>
To: Doug Brown <doug@schmorgal.com>
Cc: Kalle Valo <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Dan Williams <dcbw@redhat.com>,
libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 2/4] wifi: libertas: only add RSN/WPA IE in lbs_add_wpa_tlv
Date: Wed, 18 Jan 2023 10:14:12 +0100 [thread overview]
Message-ID: <Y8e4ZB0YzaF6sLuX@corigine.com> (raw)
In-Reply-To: <85128345-4924-c1c9-85f0-7aebc4e40f93@schmorgal.com>
On Tue, Jan 17, 2023 at 10:35:56PM -0800, Doug Brown wrote:
> On 1/17/2023 12:59 AM, Simon Horman wrote:
> > On Mon, Jan 16, 2023 at 12:21:24PM -0800, Doug Brown wrote:
> > > [You don't often get email from doug@schmorgal.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> > >
> > > The existing code only converts the first IE to a TLV, but it returns a
> > > value that takes the length of all IEs into account. When there is more
> > > than one IE (which happens with modern wpa_supplicant versions for
> > > example), the returned length is too long and extra junk TLVs get sent
> > > to the firmware, resulting in an association failure.
> > >
> > > Fix this by finding the first RSN or WPA IE and only adding that. This
> > > has the extra benefit of working properly if the RSN/WPA IE isn't the
> > > first one in the IE buffer.
> > >
> > > While we're at it, clean up the code to use the available structs like
> > > the other lbs_add_* functions instead of directly manipulating the TLV
> > > buffer.
> > >
> > > Signed-off-by: Doug Brown <doug@schmorgal.com>
> > > ---
> > > drivers/net/wireless/marvell/libertas/cfg.c | 28 +++++++++++++--------
> > > 1 file changed, 18 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/drivers/net/wireless/marvell/libertas/cfg.c b/drivers/net/wireless/marvell/libertas/cfg.c
> > > index 3e065cbb0af9..3f35dc7a1d7d 100644
> > > --- a/drivers/net/wireless/marvell/libertas/cfg.c
> > > +++ b/drivers/net/wireless/marvell/libertas/cfg.c
> >
> > ...
> >
> > > @@ -428,14 +438,12 @@ static int lbs_add_wpa_tlv(u8 *tlv, const u8 *ie, u8 ie_len)
> > > * __le16 len
> > > * u8[] data
> > > */
> > > - *tlv++ = *ie++;
> > > - *tlv++ = 0;
> > > - tlv_len = *tlv++ = *ie++;
> > > - *tlv++ = 0;
> > > - while (tlv_len--)
> > > - *tlv++ = *ie++;
> > > - /* the TLV is two bytes larger than the IE */
> > > - return ie_len + 2;
> > > + wpatlv->header.type = cpu_to_le16(wpaie->id);
> > > + wpatlv->header.len = cpu_to_le16(wpaie->datalen);
> > > + memcpy(wpatlv->data, wpaie->data, wpaie->datalen);
> >
> > Hi Doug,
> >
> > Thanks for fixing the endiness issues with cpu_to_le16()
> > This part looks good to me now. Likewise for patch 4/4.
> >
> > One suggestion I have, which is probably taking things to far,
> > is a helper for what seems to be repeated code-pattern.
> > But I don't feel strongly about that.
>
> Thanks Simon. Is this basically what you're suggesting for a helper?
>
> static int lbs_add_ie_tlv(u8 *tlvbuf, const struct element *ie, u16 tlvtype)
> {
> struct mrvl_ie_data *tlv = (struct mrvl_ie_data *)tlvbuf;
> tlv->header.type = cpu_to_le16(tlvtype);
> tlv->header.len = cpu_to_le16(ie->datalen);
> memcpy(tlv->data, ie->data, ie->datalen);
> return sizeof(struct mrvl_ie_header) + ie->datalen;
> }
>
> And then in the two functions where I'm doing that, at the bottom:
>
> return lbs_add_ie_tlv(tlv, wpaie, wpaie->id);
> return lbs_add_ie_tlv(tlv, wpsie, TLV_TYPE_WPS_ENROLLEE);
>
> I could definitely do that to avoid repeating the chunk of code that
> fills out the struct in the two functions. A lot of the other
> lbs_add_*_tlv functions follow a similar pattern of setting up a struct
> pointer and filling out the header, so I don't think it's too crazy to
> just repeat the code twice. On the other hand, the example above does
> look pretty darn clean. I don't feel strongly either way myself.
Hi Doug,
yes, I was thinking about something like that.
And wondering if it might be reused elsewhere (in the same file).
But again, I don't feel strongly about this.
So perhaps it's something to consider in future.
next prev parent reply other threads:[~2023-01-18 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 20:21 [PATCH v3 0/4] wifi: libertas: IE handling fixes Doug Brown
2023-01-16 20:21 ` [PATCH v3 1/4] wifi: libertas: fix capitalization in mrvl_ie_data struct Doug Brown
2023-01-17 3:39 ` Ping-Ke Shih
2023-01-17 6:37 ` Doug Brown
2023-01-16 20:21 ` [PATCH v3 2/4] wifi: libertas: only add RSN/WPA IE in lbs_add_wpa_tlv Doug Brown
2023-01-17 8:59 ` Simon Horman
2023-01-18 6:35 ` Doug Brown
2023-01-18 9:14 ` Simon Horman [this message]
2023-01-16 20:21 ` [PATCH v3 3/4] wifi: libertas: add new TLV type for WPS enrollee IE Doug Brown
2023-01-16 20:21 ` [PATCH v3 4/4] wifi: libertas: add support for WPS enrollee IE in probe requests Doug Brown
2023-01-17 19:05 ` Dan Williams
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=Y8e4ZB0YzaF6sLuX@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=doug@schmorgal.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.