netdev - Re: [PATCH v2 0/3] l2tp: make datapath sequence number handling RFC-compliant

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130702.163442.2300932181805961904.davem@davemloft.net>
Date:	Tue, 02 Jul 2013 16:34:42 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jchapman@...alix.com
Cc:	netdev@...r.kernel.org, sergei.shtylyov@...entembedded.com
Subject: Re: [PATCH v2 0/3] l2tp: make datapath sequence number handling
 RFC-compliant

From: James Chapman <jchapman@...alix.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@...entembedded.com.

Series applied, thanks James.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html