From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: fix loop in ofo handling code and reduce its complexity
Date: Fri, 29 May 2009 15:02:41 -0700 (PDT) [thread overview]
Message-ID: <20090529.150241.92282161.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0905291552240.10088@wrl-59.cs.helsinki.fi>
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Fri, 29 May 2009 16:03:45 +0300 (EEST)
> Somewhat luckily, I was looking into these parts with very fine
> comb because I've made somewhat similar changes on the same
> area (conflicts that arose weren't that lucky though). The loop
> was very much overengineered recently in commit 915219441d566
> (tcp: Use SKB queue and list helpers instead of doing it
> by-hand), while it basically just wants to know if there are
> skbs after 'skb'.
>
> Also it got broken because skb1 = skb->next got translated into
> skb1 = skb1->next (though abstracted) improperly. Note that
> 'skb1' is pointing to previous sk_buff than skb or NULL if at
> head. Two things went wrong:
> - We'll kfree 'skb' on the first iteration instead of the
> skbuff following 'skb' (it would require required SACK reneging
> to recover I think).
> - The list head case where 'skb1' is NULL is checked too early
> and the loop won't execute whereas it previously did.
>
> Conclusion, mostly revert the recent changes which makes the
> cset very messy looking but using proper accessor in the
> previous-like version.
>
> The effective changes against the original can be viewed with:
> git-diff 915219441d566f1da0caa0e262be49b666159e17^ \
> net/ipv4/tcp_input.c | sed -n -e '57,70 p'
>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Applied, thanks a lot for catching this!
prev parent reply other threads:[~2009-05-29 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 13:03 [PATCH net-next] tcp: fix loop in ofo handling code and reduce its complexity Ilpo Järvinen
2009-05-29 22:02 ` David Miller [this message]
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=20090529.150241.92282161.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).