From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"David S. Miller" <davem@davemloft.net>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: linux-next: manual merge of the tip tree with the wireless tree
Date: Tue, 17 May 2011 00:05:58 -0700 [thread overview]
Message-ID: <20110517070558.GP2573@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110517131417.731cf095.sfr@canb.auug.org.au>
Hello!
One of these is mine in -tip (0744371aeb). Please let me know what
I should be doing about it.
Thanx, Paul
On Tue, May 17, 2011 at 01:14:17PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in
> net/mac80211/agg-tx.c between commit ec034b208dc8 ("mac80211: fix TX
> a-MPDU locking") from the wireless tree and commit 0744371aeba7
> ("net,rcu: convert call_rcu(kfree_tid_tx) to kfree_rcu()") from the tip
> tree.
>
> Just context changes. I fixed it up (see below) and can carry the fix as
> necessary.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc net/mac80211/agg-tx.c
> index cd5125f,53defaf..0000000
> --- a/net/mac80211/agg-tx.c
> +++ b/net/mac80211/agg-tx.c
> @@@ -136,22 -136,6 +136,14 @@@ void ieee80211_send_bar(struct ieee8021
> ieee80211_tx_skb(sdata, skb);
> }
>
> +void ieee80211_assign_tid_tx(struct sta_info *sta, int tid,
> + struct tid_ampdu_tx *tid_tx)
> +{
> + lockdep_assert_held(&sta->ampdu_mlme.mtx);
> + lockdep_assert_held(&sta->lock);
> + rcu_assign_pointer(sta->ampdu_mlme.tid_tx[tid], tid_tx);
> +}
> +
> - static void kfree_tid_tx(struct rcu_head *rcu_head)
> - {
> - struct tid_ampdu_tx *tid_tx =
> - container_of(rcu_head, struct tid_ampdu_tx, rcu_head);
> -
> - kfree(tid_tx);
> - }
> -
> int ___ieee80211_stop_tx_ba_session(struct sta_info *sta, u16 tid,
> enum ieee80211_back_parties initiator,
> bool tx)
> @@@ -162,19 -146,16 +154,19 @@@
>
> lockdep_assert_held(&sta->ampdu_mlme.mtx);
>
> - if (!tid_tx)
> - return -ENOENT;
> -
> spin_lock_bh(&sta->lock);
>
> + tid_tx = rcu_dereference_protected_tid_tx(sta, tid);
> + if (!tid_tx) {
> + spin_unlock_bh(&sta->lock);
> + return -ENOENT;
> + }
> +
> if (test_bit(HT_AGG_STATE_WANT_START, &tid_tx->state)) {
> /* not even started yet! */
> - rcu_assign_pointer(sta->ampdu_mlme.tid_tx[tid], NULL);
> + ieee80211_assign_tid_tx(sta, tid, NULL);
> spin_unlock_bh(&sta->lock);
> - call_rcu(&tid_tx->rcu_head, kfree_tid_tx);
> + kfree_rcu(tid_tx, rcu_head);
> return 0;
> }
>
next prev parent reply other threads:[~2011-05-17 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 3:14 linux-next: manual merge of the tip tree with the wireless tree Stephen Rothwell
2011-05-17 7:05 ` Paul E. McKenney [this message]
2011-05-17 7:21 ` Stephen Rothwell
2011-05-17 8:09 ` Ingo Molnar
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=20110517070558.GP2573@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=johannes.berg@intel.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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