Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] nl80211: New command for adding extra IE(s) into management frames
Date: Mon, 12 Jan 2009 15:48:22 +0100	[thread overview]
Message-ID: <1231771702.3591.2.camel@johannes> (raw)
In-Reply-To: <20090112142646.GB12109@jm.kir.nu>

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

On Mon, 2009-01-12 at 16:26 +0200, Jouni Malinen wrote:

> +	/* Extra IE data for management frames */
> +	u8 *ie_probereq;
> +	size_t ie_probereq_len;
> +	u8 *ie_proberesp;
> +	size_t ie_proberesp_len;
> +	u8 *ie_auth;
> +	size_t ie_auth_len;
> +	u8 *ie_assocreq;
> +	size_t ie_assocreq_len;
> +	u8 *ie_reassocreq;
> +	size_t ie_reassocreq_len;
> +	u8 *ie_deauth;
> +	size_t ie_deauth_len;
> +	u8 *ie_disassoc;
> +	size_t ie_disassoc_len;

It'd be more memory efficient on 64-bit to not alternate between 64 and
32 bit values, but I don't really care too much in this struct.

Should we sanity-check the input? E.g. in nl80211, ensure that it's
(<type><len><data...>)* with <len> being correct and no final padding?
And maybe that there isn't anything in those IEs that we've already
added, like an SSID?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-01-12 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 12:26 [RFC] nl80211: New command for adding extra IE(s) into management frames Jouni Malinen
2009-01-12 13:08 ` Johannes Berg
2009-01-12 13:50   ` Jouni Malinen
2009-01-12 14:26   ` Jouni Malinen
2009-01-12 14:48     ` Johannes Berg [this message]
2009-01-12 15:03       ` Jouni Malinen
2009-01-12 15:07         ` 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=1231771702.3591.2.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --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