Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ron Rindjunsky <ron.rindjunsky@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: blockack sessions vs. sta removal
Date: Thu, 21 Feb 2008 15:17:43 +0100	[thread overview]
Message-ID: <1203603463.4462.1.camel@johannes.berg> (raw)

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

Hi Ron,

I was looking through some kernel oops with removing a driver
(unregister_hw()) while an AP is active and noticed that we don't clean
up, i.e. call ieee80211_sta_stop_rx_ba_session(), when a sta structure
is deleted. I think that's a bug.

johannes

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

             reply	other threads:[~2008-02-21 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 14:17 Johannes Berg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-21 14:20 blockack sessions vs. sta removal 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=1203603463.4462.1.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ron.rindjunsky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox