From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: [PATCH 2.6.30] mac80211: correct fragmentation threshold check
Date: Thu, 30 Apr 2009 14:29:28 -0400 [thread overview]
Message-ID: <20090430182927.GB9323@tuxdriver.com> (raw)
In-Reply-To: <1241040956.5067.1.camel@johannes.local>
Does there happen to be a bugzilla somewhere that corresponds to this?
On Wed, Apr 29, 2009 at 11:35:56PM +0200, Johannes Berg wrote:
> The fragmentation threshold is defined to be including the
> FCS, and the code that sets the TX_FRAGMENTED flag correctly
> accounts for those four bytes. The code that verifies this
> doesn't though, which could lead to spurious warnings and
> frames being dropped although everything is ok. Correct the
> code by accounting for the FCS.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> ---
> net/mac80211/tx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- wireless-testing.orig/net/mac80211/tx.c 2009-04-29 22:27:51.000000000 +0200
> +++ wireless-testing/net/mac80211/tx.c 2009-04-29 22:28:35.000000000 +0200
> @@ -788,7 +788,7 @@ ieee80211_tx_h_fragment(struct ieee80211
> hdrlen = ieee80211_hdrlen(hdr->frame_control);
>
> /* internal error, why is TX_FRAGMENTED set? */
> - if (WARN_ON(skb->len <= frag_threshold))
> + if (WARN_ON(skb->len + FCS_LEN <= frag_threshold))
> return TX_DROP;
>
> /*
>
>
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-04-30 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 21:35 [PATCH 2.6.30] mac80211: correct fragmentation threshold check Johannes Berg
2009-04-30 18:29 ` John W. Linville [this message]
2009-04-30 18:37 ` 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=20090430182927.GB9323@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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