netdev - Re: [PATCH net v3] geneve: Refine MTU limit

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] [day] [month] [year] [list]

Message-ID: <CAEh+42ijouX7nqF1uz1mmn9HkvoYNmbnB0iosMJ7whV-SgmRmQ@mail.gmail.com>
Date:	Thu, 18 Feb 2016 10:35:55 -0800
From:	Jesse Gross <jesse@...nel.org>
To:	David Wragg <david@...ve.works>
Cc:	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	ovs dev <dev@...nvswitch.org>,
	Tom Herbert <tom@...bertland.com>
Subject: Re: [PATCH net v3] geneve: Refine MTU limit

On Thu, Feb 18, 2016 at 9:43 AM, David Wragg <david@...ve.works> wrote:
> Calculate the maximum MTU taking into account the size of headers
> involved in GENEVE encapsulation, as for other tunnel types.
>
> Changes in v3:
> - Correct comment style
> Changes in v2:
> - Conform more closely to ip_tunnel_change_mtu
> - Exclude GENEVE options from max MTU calculation
>
> Signed-off-by: David Wragg <david@...ve.works>

Acked-by: Jesse Gross <jesse@...nel.org>