From: Brandon Craig Rhodes <brandon@rhodesmill.org>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: netdev@vger.kernel.org
Subject: Re: TKIP encryption should allocate enough tailroom
Date: Wed, 17 Jan 2007 12:38:44 -0500 [thread overview]
Message-ID: <87odox4kpn.fsf@ten22.rhodesmill.org> (raw)
In-Reply-To: <45AE5B8C.2070407@lwfinger.net> (Larry Finger's message of "Wed, 17 Jan 2007 11:23:24 -0600")
Larry Finger <larry.finger@lwfinger.net> writes:
> Brandon Craig Rhodes wrote:
>
>> Having further reviewed my code, I have changed my mind; the
>> ieee80211_crypt_tkip routines are not designed to be responsible for
>> creating enough headroom and tailroom. The "hostap" driver should be
>> doing this.
>
> This makes sense. I have used the bcm43xx driver with WPA-PSK TKIP
> encryption for at least a year, and I have never seen this error.
>From what I can tell, even people using the "hostap" driver never see
this error! The kernel must allocate such large skb's in normal
operation that there is always more than enough tailroom for twelve
bytes of TKIP encryption.
In my case, packets are arriving on the physical machine from a Xen
virtual machine that the physical machine is hosting. The Xen code
receiving the packets must allocate much tighter skb's than does the
normal kernel code that receives packets from hardware. (Perhaps
because Xen knows the packet size ahead of time, whereas hardware
drivers do not?) Searching for the error message:
kernel: Invalid packet for Michael MIC add (tailroom=6 hdr_len=24 skb->len=92)
on Google returned, if I recall, only references to the kernel source
code itself - which always gives me the sinking feeling that I've
gotten myself into a configuration shared with no one else on earth!
--
Brandon Craig Rhodes brandon@rhodesmill.org http://rhodesmill.org/brandon
next prev parent reply other threads:[~2007-01-17 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 2:31 TKIP encryption should allocate enough tailroom Brandon Craig Rhodes
2007-01-17 3:39 ` Mitchell Blank Jr
2007-01-17 3:34 ` Brandon Craig Rhodes
2007-01-17 6:34 ` Herbert Xu
2007-01-17 7:18 ` Herbert Xu
2007-01-17 3:50 ` Michael Wu
2007-01-17 16:46 ` Brandon Craig Rhodes
2007-01-17 17:23 ` Larry Finger
2007-01-17 17:38 ` Brandon Craig Rhodes [this message]
2007-01-18 13:16 ` Pekka Pietikainen
2007-01-18 13:55 ` Brandon Craig Rhodes
2007-01-19 12:23 ` Pekka Pietikainen
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=87odox4kpn.fsf@ten22.rhodesmill.org \
--to=brandon@rhodesmill.org \
--cc=larry.finger@lwfinger.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox