All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
	Intel Linux Wireless <ilw@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless-2.6] iwlagn: fix "Received BA when not expected"
Date: Fri, 29 Apr 2011 15:57:12 +0200	[thread overview]
Message-ID: <20110429135711.GA5537@redhat.com> (raw)
In-Reply-To: <1303992593.3558.7.camel@jlt3.sipsolutions.net>

On Thu, Apr 28, 2011 at 02:09:53PM +0200, Johannes Berg wrote:
> > > Maybe we should make it clear here that it's about non-data frames and
> > > remove the multicast check since that ought to be handled in the other
> > > path?
> > 
> > We call iwl_sta_modify_sleep_tx_count(priv, sta_id, 1); for any frame
> > as long as some other conditions are true.
> 
> That can only happen in AP mode, and if the station is asleep, I don't
> think it's a concern.
> 
> > Also multicast frames are important. When we send data and multicast
> > frame we probably modify 
> > 
> > priv->stations[sta_id].tid[tid]
> > 
> > with wrong sta_id (other station with unicast address), what make related
> > aggregation data wrong for that other station.
> 
> Yeah, but multicast is already handled properly, since in that case
> info->control.sta will be set to NULL by mac80211. Keep in mind that
> again this is AP mode only, since a client connected to an AP never
> sends real multicast frames (if it sends 802.3 multicast frames they're
> still unicast to the AP).

We use sta_id for building tx command in:

if (info->control.hw_key)
	iwlagn_tx_cmd_build_hwcrypto(priv, info, tx_cmd, skb, sta_id);

/* TODO need this for burst mode later on */
iwlagn_tx_cmd_build_basic(priv, skb, tx_cmd, info, hdr, sta_id);

so problems seems to be that the firmware do not handle
unicast sta_id for management frames. I'll repost patches
that check only ieee80211_is_data(fc).

BTW, iwlagn_tx_skb function needs serious cleanup, it's
completely unreadable!

Stanislaw

      reply	other threads:[~2011-04-29 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 11:10 [PATCH wireless-2.6] iwlagn: fix "Received BA when not expected" Stanislaw Gruszka
2011-04-28 11:37 ` Johannes Berg
2011-04-28 11:41   ` Johannes Berg
2011-04-28 11:59   ` Stanislaw Gruszka
2011-04-28 12:09     ` Johannes Berg
2011-04-29 13:57       ` Stanislaw Gruszka [this message]

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=20110429135711.GA5537@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.