From: David Miller <davem@davemloft.net>
To: jchapman@katalix.com
Cc: netdev@vger.kernel.org, sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH v2 0/3] l2tp: make datapath sequence number handling RFC-compliant
Date: Tue, 02 Jul 2013 16:34:42 -0700 (PDT) [thread overview]
Message-ID: <20130702.163442.2300932181805961904.davem@davemloft.net> (raw)
In-Reply-To: <1372793340-17883-1-git-send-email-jchapman@katalix.com>
From: James Chapman <jchapman@katalix.com>
Date: Tue, 2 Jul 2013 20:28:57 +0100
> L2TP data sequence numbers, if enabled, ensure in-order delivery. A
> receiver may reorder data packets, or simply drop out-of-sequence
> packets. If reordering is not enabled, the current implementation does
> not handle data packet loss correctly, which can result in a stalled
> L2TP session datapath as soon as the first packet is lost. Most L2TP
> users either disable sequence numbers or enable data packet reordering
> when sequence numbers are used to circumvent the issue. This patch
> series fixes the problem, and makes the L2TP sequence number handling
> RFC-compliant.
>
> v2 incorporates string format changes requested by sergei.shtylyov@cogentembedded.com.
Series applied, thanks James.
prev parent reply other threads:[~2013-07-02 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 19:28 [PATCH v2 0/3] l2tp: make datapath sequence number handling RFC-compliant James Chapman
2013-07-02 19:28 ` [PATCH v2 1/3] l2tp: do data sequence number handling in a separate func James Chapman
2013-07-02 19:28 ` [PATCH v2 2/3] l2tp: make datapath sequence number support RFC-compliant James Chapman
2013-07-02 19:29 ` [PATCH v2 3/3] l2tp: make datapath resilient to packet loss when sequence numbers enabled James Chapman
2013-07-02 23:34 ` 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=20130702.163442.2300932181805961904.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).