From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org
Subject: Re: [PATCH] Assign next hop address to pending mesh frames once the path is resolved.
Date: Wed, 08 Jul 2009 12:40:13 +0200 [thread overview]
Message-ID: <1247049613.4755.65.camel@johannes.local> (raw)
In-Reply-To: <1247032403-8312-1-git-send-email-javier@cozybit.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Tue, 2009-07-07 at 22:53 -0700, Javier Cardona wrote:
> Regression. Frames transmitted when a mesh path was wating to be resolved were
> being transmitted with an invalid Receiver Address.
> - rcu_assign_pointer(mpath->next_hop, sta);
> + struct sk_buff *skb, *skb_first = NULL;
> + struct ieee80211_hdr *hdr;
> +
> + rcu_read_lock();
> + mpath->next_hop = sta;
> +
> + while ((skb = skb_dequeue(&mpath->frame_queue)) != skb_first) {
> + if (!skb_first)
> + skb_first = skb;
> + hdr = (struct ieee80211_hdr *) skb->data;
> + memcpy(hdr->addr1, sta->sta.addr, ETH_ALEN);
> + skb_queue_tail(&mpath->frame_queue, skb);
> + }
> + if (skb_first)
> + skb_queue_tail(&mpath->frame_queue, skb_first);
> +
> + rcu_read_unlock();
Since skb queues have a locks, why use rcu too?
Also I think you should probably use a different pattern -- this looks
prone to breakage, maybe something like
sk_buff_head tmpq;
unsigned long flags;
__skb_queue_head_init(&tmpq);
spin_lock_irqsave(&frame_queue->lock);
while (skb = __skb_dequeue(&frame_queue)) {
hdr = (struct ieee80211_hdr *) skb->data;
memcpy(hdr->addr1, sta->sta.addr, ETH_ALEN);
__skb_queue_tail(&tmpq, skb);
}
skb_queue_splice(&tmpq, frame_queue);
spin_unlock_irqrestore(&frame_queue->lock);
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-08 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 5:53 [PATCH] Assign next hop address to pending mesh frames once the path is resolved Javier Cardona
2009-07-08 10:40 ` Johannes Berg [this message]
2009-07-08 17:02 ` Javier Cardona
2009-07-09 21:42 ` [PATCH v2] " Javier Cardona
2009-07-09 21:54 ` 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=1247049613.4755.65.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
/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