Linux wireless drivers development
 help / color / mirror / Atom feed
* blockack sessions vs. sta removal
@ 2008-02-21 14:17 Johannes Berg
  0 siblings, 0 replies; 2+ messages in thread
From: Johannes Berg @ 2008-02-21 14:17 UTC (permalink / raw)
  To: Ron Rindjunsky; +Cc: linux-wireless

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* blockack sessions vs. sta removal
@ 2008-02-21 14:20 Johannes Berg
  0 siblings, 0 replies; 2+ messages in thread
From: Johannes Berg @ 2008-02-21 14:20 UTC (permalink / raw)
  To: Ron Rindjunsky; +Cc: linux-wireless

[-- Attachment #1: Type: text/plain, Size: 448 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.

Also, the code in ieee80211_stop() that iterates the sta_list should
have some locking, no?

I really need to work on cleaning up the sta info code, it really is a
huge mess.

johannes

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-02-21 19:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-21 14:17 blockack sessions vs. sta removal Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2008-02-21 14:20 Johannes Berg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox