Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Luciano Coelho <coelho@ti.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: don't drop frames where skb->len < 24 in ieee80211_scan_rx()
Date: Mon, 09 May 2011 16:46:39 +0200	[thread overview]
Message-ID: <1304952399.12202.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1304950753-2952-1-git-send-email-coelho@ti.com>

On Mon, 2011-05-09 at 17:19 +0300, Luciano Coelho wrote:
> This seems to be a leftover from the old days, when we didn't support
> any frames that didn't contain the full ieee802.11 header.  This is
> not the case anymore.  It does not cause problems now, because they
> are only dropped during scan.  But when scheduled scans get merged,
> this would become a problem because we would drop all small frames
> while scheduled scan is running.
> 
> Cc: Johannes Berg <johannes@sipsolutions.net>
> Signed-off-by: Luciano Coelho <coelho@ti.com>
> ---
>  net/mac80211/scan.c |    3 ---
>  1 files changed, 0 insertions(+), 3 deletions(-)
> 
> diff --git a/net/mac80211/scan.c b/net/mac80211/scan.c
> index 489b6ad..b7a39c4 100644
> --- a/net/mac80211/scan.c
> +++ b/net/mac80211/scan.c
> @@ -169,9 +169,6 @@ ieee80211_scan_rx(struct ieee80211_sub_if_data *sdata, struct sk_buff *skb)
>  	if (ieee80211_is_ctl(fc))
>  		return RX_CONTINUE;
>  
> -	if (skb->len < 24)
> -		return RX_DROP_MONITOR;
> -

You can't just delete it, we use mgmt->da at least in this code path.
You should just change RX_DROP_MONITOR to RX_CONTINUe here I think.

johannes


  reply	other threads:[~2011-05-09 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 14:19 [PATCH] mac80211: don't drop frames where skb->len < 24 in ieee80211_scan_rx() Luciano Coelho
2011-05-09 14:46 ` Johannes Berg [this message]
2011-05-09 16:13   ` Luciano Coelho
2011-05-09 16:15     ` [PATCH v2] " Luciano Coelho

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=1304952399.12202.3.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=coelho@ti.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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