netdev - Re: [PATCH net-next] openvswitch: Set internal device max mtu to ETH_MAX

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]

Date:   Wed, 15 Feb 2017 12:40:39 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     jarno@....org
Cc:     netdev@...r.kernel.org, jarod@...hat.com, pshelar@....org
Subject: Re: [PATCH net-next] openvswitch: Set internal device max mtu to
 ETH_MAX_MTU.

From: Jarno Rajahalme <jarno@....org>
Date: Tue, 14 Feb 2017 21:16:28 -0800

> Commit 91572088e3fd ("net: use core MTU range checking in core net
> infra") changed the openvswitch internal device to use the core net
> infra for controlling the MTU range, but failed to actually set the
> max_mtu as described in the commit message, which now defaults to
> ETH_DATA_LEN.
> 
> This patch fixes this by setting max_mtu to ETH_MAX_MTU after
> ether_setup() call.
> 
> Fixes: 91572088e3fd ("net: use core MTU range checking in core net infra")
> Signed-off-by: Jarno Rajahalme <jarno@....org>

Applied, thank you.