Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock

netdev

Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock

To:	Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Subject:	Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock
From:	"David S. Miller" <davem@xxxxxxxxxx>
Date:	Wed, 15 Oct 2003 22:10:20 -0700
Cc:	netdev@xxxxxxxxxxx
In-reply-to:	<20031015113648.GD1174@xxxxxxxxxxxxxxxx>
References:	<20031012131344.GH16182@xxxxxxxxxxxxxxxx> <20031013124930.0e75a325.davem@xxxxxxxxxx> <20031015113648.GD1174@xxxxxxxxxxxxxxxx>
Sender:	netdev-bounce@xxxxxxxxxxx

On Wed, 15 Oct 2003 08:36:48 -0300
Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx> wrote:

> Em Mon, Oct 13, 2003 at 12:49:30PM -0700, David S. Miller escreveu:
> > Let's do one thing at a time.  First, fix the original bug
> > in tcp_ipv4.c by just putting your inet_rcv_saddr() shorthand
> > right there in tcp_ipv4.c and name it tcp4_rcv_saddr() or
> > something like that.
 ... 
> :) Here is the first part:

Perfect, patch applied.

Thanks.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock, Arnaldo Carvalho de Melo Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock, David S. Miller Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock, Arnaldo Carvalho de Melo Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock, David S. Miller <=

Previous by Date:	Re: 6to4/SIT and IP DF, David S. Miller
Next by Date:	Re: 6to4/SIT and IP DF, David Stevens
Previous by Thread:	Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock, Arnaldo Carvalho de Melo
Next by Thread:	[PATCH 2/10] [bonding 2.6] fix monitoring functions, Amir Noam
Indexes:	[Date] [Thread] [Top] [All Lists]