netdev - Re: [net-next PATCH 3/4] vxlan: Enforce IP ID verification on outer headers

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20160307.140947.1831226984496616218.davem@davemloft.net>
Date:	Mon, 07 Mar 2016 14:09:47 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	gerlitz.or@...il.com
Cc:	aduyck@...antis.com, netdev@...r.kernel.org
Subject: Re: [net-next PATCH 3/4] vxlan: Enforce IP ID verification on
 outer headers

From: Or Gerlitz <gerlitz.or@...il.com>
Date: Mon, 7 Mar 2016 20:05:20 +0200

> On Mon, Mar 7, 2016 at 7:22 PM, Alexander Duyck <aduyck@...antis.com> wrote:
>> This change enforces the IP ID verification on outer headers.  As a result
>> if the DF flag is not set on the outer header we will force the flow to be
>> flushed in the event that the IP ID is out of sequence with the existing
>> flow.
> 
> Can you please state the precise requirement for aggregation w.r.t IP
> IDs here? and point to where/how this is enforced, e.g for
> non-tunneled TCP GRO-ing?

I also didn't see a nice "PATCH 0/4" posting explaining this series and
I'd really like to see that.