| To: | Thomas Graf <tgraf@xxxxxxx> |
|---|---|
| Subject: | Re: race in net/ipv4/ipip.c ? |
| From: | Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx> |
| Date: | Wed, 12 Jan 2005 14:09:40 +0100 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20050112125336.GH26856@xxxxxxxxxxxxxx> |
| References: | <20050112122300.GA12155@xxxxxxxxxxxxxxxxx> <20050112125336.GH26856@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
On Wed, Jan 12, 2005 at 01:53:36PM +0100, Thomas Graf wrote:
> > static void ipip_tunnel_link(struct ipip_tunnel *t)
> > {
> > struct ipip_tunnel **tp = ipip_bucket(t);
> >
> > t->next = *tp;
> > write_lock_bh(&ipip_lock);
> > *tp = t;
> > write_unlock_bh(&ipip_lock);
> > }
> >
> > Shouldn't the "t->next = *tp" be done inside the write lock?
>
> Why do you think so? linking may only happen on new tunnels
> so they can't be found before they're assigned to the bucket.
> dev_hold is called correctly so dev->priv usage is safe as
> well.
What if you add two tunnels at the same time? (Or is that perhaps
synchronised on a higher level?)
--L
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: race in net/ipv4/ipip.c ?, YOSHIFUJI Hideaki / 吉藤英明 |
|---|---|
| Next by Date: | Re: race in net/ipv4/ipip.c ?, Thomas Graf |
| Previous by Thread: | Re: race in net/ipv4/ipip.c ?, David S. Miller |
| Next by Thread: | Iproute2: update, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |