From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: chris2553@googlemail.com, linux-wireless@vger.kernel.org
Subject: Re: Warning emited by 2.6.24-rc6-git5
Date: Sat, 29 Dec 2007 16:14:55 +0100 [thread overview]
Message-ID: <200712291614.55732.IvDoorn@gmail.com> (raw)
In-Reply-To: <1198939208.4172.46.camel@johannes.berg>
On Saturday 29 December 2007, Johannes Berg wrote:
>
> > Well Ralink doesn't seem to add this padding since this bug appeared,
> > remember all bytes from the DMA was copied to the skb buffer so if there
> > was any padding included it would have been copied as well. ;)
>
> Not necessarily, Broadcom hardware adds the padding in front of the
> 802.11 header so if you'd start copying with the 802.11 header you'd run
> into the same thing. A quick look at the rt2x00pci.c file doesn't
> suggest that there's anything variable about the RX header though so I
> guess that indeed this may be a problem.
>
> > Anyway, I have worked on a fix for the padding and I'll commit it to
> > rt2x00.git first to see if anybody reports any problems with it before
> > sending it to wireless-dev.
>
> Great. I just posted a similar fix in the other thread for zd1211, does
> that look similar to yours as well? Should we have a static inline with
> this code "ieee80211_needs_padding()" or something?
My code looks more like:
header_size = ieee80211_get_hdrlen_from_skb(entry->skb);
if (header_size % 4 == 2) {
/*
* Move entire frame 2 bytes to the front.
*/
skb_push(entry->skb, 2);
memmove(entry->skb->data, entry->skb->data + 2,
entry->skb->len - 2);
}
Ivo
next prev parent reply other threads:[~2007-12-29 15:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 9:42 Warning emited by 2.6.24-rc6-git5 Chris Clayton
2007-12-29 9:54 ` Johannes Berg
2007-12-29 10:21 ` Ivo van Doorn
2007-12-29 10:26 ` Johannes Berg
2007-12-29 10:36 ` Johannes Berg
2007-12-29 11:47 ` Ivo van Doorn
2007-12-29 11:59 ` Johannes Berg
2007-12-29 12:01 ` Johannes Berg
2007-12-29 14:29 ` Ivo van Doorn
2007-12-29 14:40 ` Johannes Berg
2007-12-29 15:14 ` Ivo van Doorn [this message]
2007-12-30 11:49 ` Chris Clayton
2007-12-30 12:11 ` Ivo van Doorn
2007-12-30 19:26 ` Chris Clayton
2007-12-30 22:01 ` Ivo van Doorn
2007-12-31 7:27 ` Kalle Valo
2007-12-31 7:56 ` Ivo Van Doorn
2008-01-02 6:32 ` Chris Clayton
2008-01-02 19:02 ` Ivo van Doorn
2008-01-04 17:09 ` Chris Clayton
2008-01-06 7:49 ` Andrew Price
2008-01-08 6:03 ` Chris Clayton
2008-01-02 8:11 ` Johannes Berg
2008-01-02 19:12 ` Ivo van Doorn
2008-01-08 15:44 ` Tomas Winkler
2008-01-08 17:09 ` Johannes Berg
2008-01-08 17:22 ` Johannes Berg
2008-01-08 19:43 ` Tomas Winkler
2008-01-08 20:02 ` Michael Buesch
2008-01-08 23:18 ` Tomas Winkler
2008-01-09 12:49 ` 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=200712291614.55732.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=chris2553@googlemail.com \
--cc=johannes@sipsolutions.net \
--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;
as well as URLs for NNTP newsgroup(s).