linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org,
	Benoit Papillault <benoit.papillault@free.fr>
Subject: Re: [PATCH v3 4/4] rt2x00: Only remove L2 padding in received frames if there is payload.
Date: Tue, 01 Dec 2009 23:09:14 +0100	[thread overview]
Message-ID: <4B15940A.8070304@gmail.com> (raw)
In-Reply-To: <200912012257.02397.IvDoorn@gmail.com>

On 12/01/09 22:57, Ivo van Doorn wrote:
> On Tuesday 01 December 2009, Gertjan van Wingerde wrote:
>> On 12/01/09 20:16, Ivo van Doorn wrote:
>>> On Monday 30 November 2009, Gertjan van Wingerde wrote:
>>>> L2 padding will only be present when there is actual payload present.
>>>>
>>>> Signed-off-by: Gertjan van Wingerde <gwingerde@gmail.com>
>>>> ---
>>>>  drivers/net/wireless/rt2x00/rt2x00dev.c |    4 +++-
>>>>  1 files changed, 3 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/drivers/net/wireless/rt2x00/rt2x00dev.c b/drivers/net/wireless/rt2x00/rt2x00dev.c
>>>> index ca2bcc0..b93731b 100644
>>>> --- a/drivers/net/wireless/rt2x00/rt2x00dev.c
>>>> +++ b/drivers/net/wireless/rt2x00/rt2x00dev.c
>>>> @@ -401,7 +401,9 @@ void rt2x00lib_rxdone(struct rt2x00_dev *rt2x00dev,
>>>>  	    (rxdesc.flags & RX_FLAG_IV_STRIPPED))
>>>>  		rt2x00crypto_rx_insert_iv(entry->skb, header_length,
>>>>  					  &rxdesc);
>>>> -	else if (rxdesc.dev_flags & RXDONE_L2PAD)
>>>> +	else if (header_length &&
>>>> +		 (rxdesc.size > header_length) &&
>>>> +		 (rxdesc.dev_flags & RXDONE_L2PAD))
>>>>  		rt2x00queue_remove_l2pad(entry->skb, header_length);
>>>>  	else
>>>>  		rt2x00queue_align_payload(entry->skb, header_length);
>>>
>>> Is there a scenario where header_lenght can be 0?
>>> And if there is, shouldn't we have bailed-out completely already?
>>>
>>
>> Actually, there is. ieee80211_get_hdrlen_from_skb returns 0 when it detects that
>> the skb is actually shorter than it should be (according to the frame type indicated
>> by the frame_control field).
>> I'm using that here to check whether actually any payload is present, as a value of 0
>> means that there isn't even a full header.
>> We should still pass on the frame in that case, for the monitor interfaces.
> 
> Ok, then we should pass it to mac80211, but we better use a goto or something to
> skip all frame manipulation (like the rt2x00crypto_rx_insert_iv and rt2x00queue_align_payload)
> as well.
> 

Good point. Can we do that as a follow-up patch?

---
Gertjan.


  reply	other threads:[~2009-12-01 22:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 21:08 [PATCH v3 0/4] Further L2 padding fixes Gertjan van Wingerde
2009-11-30 21:08 ` [PATCH v3 1/4] rt2x00: " Gertjan van Wingerde
2009-11-30 21:08   ` [PATCH v3 2/4] rt2x00: Remove SKBDESC_L2_PADDED flag Gertjan van Wingerde
2009-11-30 21:08     ` [PATCH v3 3/4] rt2x00: Reorganize L2 padding inserting function Gertjan van Wingerde
2009-11-30 21:08       ` [PATCH v3 4/4] rt2x00: Only remove L2 padding in received frames if there is payload Gertjan van Wingerde
2009-12-01 19:16         ` Ivo van Doorn
2009-12-01 21:08           ` Gertjan van Wingerde
2009-12-01 21:57             ` Ivo van Doorn
2009-12-01 22:09               ` Gertjan van Wingerde [this message]
2009-12-02  7:52                 ` Ivo Van Doorn
2009-12-01 21:58         ` Ivo van Doorn
2009-12-01 19:13       ` [PATCH v3 3/4] rt2x00: Reorganize L2 padding inserting function Ivo van Doorn
2009-12-01 21:05         ` Gertjan van Wingerde
2009-12-01 21:58       ` Ivo van Doorn
2009-12-01 19:07     ` [PATCH v3 2/4] rt2x00: Remove SKBDESC_L2_PADDED flag Ivo van Doorn
2009-12-01 19:07   ` [PATCH v3 1/4] rt2x00: Further L2 padding fixes Ivo van Doorn
2009-11-30 23:46 ` [rt2x00-users] [PATCH v3 0/4] " Benoit PAPILLAULT
2009-12-01 21:30   ` Gertjan van Wingerde
2009-12-02  9:54     ` Benoit PAPILLAULT
2009-12-03  9:32       ` Gertjan van Wingerde
2009-12-03 18:36         ` Ivo van Doorn
2009-12-03 21:36           ` Benoit PAPILLAULT
2009-12-04  7:53             ` Ivo Van Doorn

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=4B15940A.8070304@gmail.com \
    --to=gwingerde@gmail.com \
    --cc=benoit.papillault@free.fr \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.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 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).