Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: Broken fragmentation
Date: Thu, 19 Jun 2008 20:16:59 +0200	[thread overview]
Message-ID: <1213899419.8967.59.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240806191113nd6a221eiac9648edd3404a80@mail.gmail.com> (sfid-20080619_201352_223234_D04C033E)

[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]

On Thu, 2008-06-19 at 21:13 +0300, Tomas Winkler wrote:
> On Thu, Jun 19, 2008 at 6:26 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Thu, 2008-06-19 at 17:45 +0300, Tomas Winkler wrote:
> >> On Thu, Jun 19, 2008 at 4:24 PM, Johannes Berg
> >> <johannes@sipsolutions.net> wrote:
> >> > On Thu, 2008-06-19 at 16:08 +0300, Tomas Winkler wrote:
> >> >> On Thu, Jun 19, 2008 at 3:23 PM, Johannes Berg
> >> >> <johannes@sipsolutions.net> wrote:
> >> >> >
> >> >> >> > Now it crashes in the driver...maybe the txinfo to cb changes. Looking into it.
> >> >> >> > Tomas
> >> >> >> Looks like this is the second part keyconf is null
> >> >> >
> >> >> > Part? You mean fragment? What encryption algorithm? I've quickly looked
> >> >> > and all of them seem to do the control.hw_key assignment in their
> >> >> > respective _skb handler so it should be done for all fragments.
> >> >>
> >> >> The problem is w/o crypto
> >> >> I think this is not set on each fragment
> >> >> info->flags |= IEEE80211_TX_CTL_DO_NOT_ENCRYPT;
> >> >
> >> > Ouch, you're right, the whole tx info isn't properly initialised for
> >> > fragments.
> >> >
> >> > Can you try putting
> >> >
> >> > memcpy(frag->cb, first->cb, sizeof(first->cb));
> >> >
> >> > at around line 690 of tx.c where this code is?
> >> >
> >> >                frag->priority = first->priority;
> >> >                skb_reserve(frag, tx->local->tx_headroom +
> >> >                                  IEEE80211_ENCRYPT_HEADROOM);
> >> >
> >> >
> >> > [now I know what the cause is. I had another patch that used skb_segment
> >> > to do the fragmentation, but that was dropped and skb_segment does copy
> >> > skb->cb while our code doesn't]
> >>
> >> No crash but still not at home. No fragmented traffic on the air...grrr.
> >
> > Hmm, ok. I'll give it a try later.
> 
> Fragments are in the air but the peer is not able to reassemble them.
> Something is wrong with the first fragment but I'm not sure yet.

Hm, ok. got a packet capture? Maybe that was broken before, I remember
having problems with fragmentation but putting it down to the
known-to-be-completely-broken AP I was using.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2008-06-19 18:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19  9:20 Broken fragmentation Tomas Winkler
2008-06-19  9:56 ` Johannes Berg
2008-06-19 11:46   ` Tomas Winkler
2008-06-19 11:57     ` Tomas Winkler
2008-06-19 12:23       ` Johannes Berg
2008-06-19 13:08         ` Tomas Winkler
2008-06-19 13:24           ` Johannes Berg
2008-06-19 14:45             ` Tomas Winkler
2008-06-19 15:26               ` Johannes Berg
2008-06-19 18:13                 ` Tomas Winkler
2008-06-19 18:16                   ` Johannes Berg [this message]
2008-06-19 21:09                     ` Tomas Winkler
2008-06-19 21:25                       ` Johannes Berg
2008-06-25  9:50                         ` Tomas Winkler
2008-06-25 10:02                           ` Johannes Berg
2008-06-25 10:30                             ` Tomas Winkler
2008-06-25 10:32                               ` Johannes Berg
2008-06-25 10:35                                 ` Tomas Winkler
2008-06-25 10:42                                   ` Johannes Berg
2008-06-25 10:59                                     ` Tomas Winkler

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=1213899419.8967.59.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.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