From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org,
"Thomas Bätzler" <t.baetzler@bringe.com>
Subject: Re: [PATCH] Fixing to check the lower bound of valid ACK
Date: Wed, 25 Jun 2008 12:50:50 +0200 [thread overview]
Message-ID: <4862230A.4040002@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0806251151400.21979@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> Hi Patrick,
>
> Lost connections was reported by Thomas Bätzler (running 2.6.25 kernel) on
> the netfilter mailing list (see the thread "Weird nat/conntrack Problem
> with PASV FTP upload"). He provided tcpdump recordings which helped to
> find a long lingering bug in conntrack.
>
> In TCP connection tracking, checking the lower bound of valid ACK could
> lead to mark valid packets as INVALID because:
>
> - We have got a "higher or equal" inequality, but the test checked
> the "higher" condition only; fixed.
> - If the packet contains a SACK option, it could occur that the ACK
> value was before the left edge of our (S)ACK "window": if a previous
> packet from the other party intersected the right edge of the window
> of the receiver, we could move forward the window parameters beyond
> accepting a valid ack. Therefore in this patch we check the rightmost
> SACK edge instead of the ACK value in the lower bound of valid (S)ACK
> test.
Applied, thanks. I'll also push this patch to -stable once
its in Linus' tree.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-06-25 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 10:13 [PATCH] Fixing to check the lower bound of valid ACK Jozsef Kadlecsik
2008-06-25 10:50 ` Patrick McHardy [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=4862230A.4040002@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=t.baetzler@bringe.com \
/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