[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39e6f6c70702280410k2d13afc7k1f870c73b6862676@mail.gmail.com>
Date: Wed, 28 Feb 2007 09:10:10 -0300
From: "Arnaldo Carvalho de Melo" <acme@...stprotocols.net>
To: "KOVACS Krisztian" <hidden@...abit.hu>
Cc: netdev@...r.kernel.org
Subject: Re: TCP minisock tcp_create_openreq_child() typo?
On 2/28/07, KOVACS Krisztian <hidden@...abit.hu> wrote:
>
> Hi,
>
> While reading TCP minisock code I've found this suspiciously looking
> code fragment:
>
> - 8< -
> struct sock *tcp_create_openreq_child(struct sock *sk, struct request_sock *req, struct sk_buff *skb)
> {
> struct sock *newsk = inet_csk_clone(sk, req, GFP_ATOMIC);
>
> if (newsk != NULL) {
> const struct inet_request_sock *ireq = inet_rsk(req);
> struct tcp_request_sock *treq = tcp_rsk(req);
> struct inet_connection_sock *newicsk = inet_csk(sk);
> struct tcp_sock *newtp;
> - 8< -
>
> The above code initializes newicsk to inet_csk(sk), isn't that supposed
> to be inet_csk(newsk)? As far as I can tell this might leave
> icsk_ack.last_seg_size zero even if we do have received data.
Good catch!
David, please apply the attached patch.
Signed-off-by: Arnaldo Carvalho de Melo <acme@...hat.com>
Thanks Krisztian!
- Arnaldo
View attachment "newicsk.patch" of type "text/x-patch" (559 bytes)
Powered by blists - more mailing lists