From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] mac80211: Use #define IEEE80211_CCMP_PN_LEN and bool
Date: Mon, 30 Mar 2015 13:05:52 -0700 [thread overview]
Message-ID: <1427745952.14276.24.camel@perches.com> (raw)
In-Reply-To: <1427745718.26117.46.camel@sipsolutions.net>
On Mon, 2015-03-30 at 22:01 +0200, Johannes Berg wrote:
> On Mon, 2015-03-30 at 09:37 -0700, Joe Perches wrote:
>
> > @@ -89,11 +90,11 @@ struct ieee80211_fragment_entry {
> > unsigned int last_frag;
> > unsigned int extra_len;
> > struct sk_buff_head skb_list;
> > - int ccmp; /* Whether fragments were encrypted with CCMP */
> > - u8 last_pn[6]; /* PN of the last fragment if CCMP was used */
> > + /* for CCMP fragments */
> > + bool ccmp; /* encrypted with CCMP */
> > + u8 last_pn[IEEE80211_CCMP_PN_LEN]; /* PN of the last fragment */
>
> I took your patch as an opportunity to check into this, and it turns out
> all of this logic is also going to be needed for GCMP. As a result, I'm
> not going to take this patch but instead we'll fix it up for GCMP (where
> using CCMP_PN_LEN would not be appropriate anyway - perhaps we need a
> union or just keep '8' which is the right size for both anyway, or we'll
> go to a u64 value or something)
No worries. Whatever's right.
prev parent reply other threads:[~2015-03-30 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 16:37 [PATCH -next] mac80211: Use #define IEEE80211_CCMP_PN_LEN and bool Joe Perches
2015-03-30 20:01 ` Johannes Berg
2015-03-30 20:05 ` Joe Perches [this message]
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=1427745952.14276.24.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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.