From: Johannes Berg <johannes@sipsolutions.net>
To: Shahar Levi <shahar_levi@ti.com>
Cc: linux-wireless@vger.kernel.org,
Luciano Coelho <luciano.coelho@nokia.com>
Subject: Re: [RFC 1/2] mac80211: Stop BA session event from device
Date: Thu, 25 Nov 2010 19:11:06 +0100 [thread overview]
Message-ID: <1290708666.3770.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1290695964-4208-1-git-send-email-shahar_levi@ti.com>
On Thu, 2010-11-25 at 16:39 +0200, Shahar Levi wrote:
> +void ieee80211_stop_rx_ba_session(struct ieee80211_vif *vif, u16 tid,
> + const u8 *addr);
missing docs
> +void ieee80211_stop_rx_ba_session(struct ieee80211_vif *vif, u16 tid,
> + const u8 *addr)
> +{
> + struct ieee80211_sub_if_data *sdata = vif_to_sdata(vif);
> + struct sta_info *sta = sta_info_get(sdata, addr);
> +
> + __ieee80211_stop_rx_ba_session(sta, tid, WLAN_BACK_INITIATOR, 0, true);
> +}
> +EXPORT_SYMBOL(ieee80211_stop_rx_ba_session);
Locking-wise, this is a disaster, as the function will acquire a mutex
that it also holds across other calls into the driver. It would seem
that this should have caused lockdep to warn you about ABBA style
deadlock since you call this with wl->mutex held, and previously you
said you were going to acquire that mutex from ampdu_action.
This should use a similar trick to the one used in TX aggregation.
johannes
next prev parent reply other threads:[~2010-11-25 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 14:39 [RFC 1/2] mac80211: Stop BA session event from device Shahar Levi
2010-11-25 14:39 ` [RFC 2/2] wl12xx: " Shahar Levi
2010-11-29 12:53 ` Luciano Coelho
2010-11-29 12:55 ` Shahar Levi
2010-11-29 12:58 ` Luciano Coelho
2010-11-29 13:24 ` Shahar Levi
2010-11-25 18:11 ` Johannes Berg [this message]
2010-11-25 18:35 ` [RFC 1/2] mac80211: " Levi, Shahar
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=1290708666.3770.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@nokia.com \
--cc=shahar_levi@ti.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.