netdev - Re: [PATCH v3 net-next] net: vxlan: use custom ndo_change

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: <20131222.180138.1233577114547473304.davem@davemloft.net>
Date:	Sun, 22 Dec 2013 18:01:38 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	dborkman@...hat.com
Cc:	stephen@...workplumber.org, netdev@...r.kernel.org
Subject: Re: [PATCH v3 net-next] net: vxlan: use custom ndo_change_mtu
 handler

From: Daniel Borkmann <dborkman@...hat.com>
Date: Wed, 18 Dec 2013 00:21:08 +0100

> When adding a new vxlan device to an "underlying carrier" (here:
> dst->remote_ifindex), the MTU size assigned to the vxlan device
> is the MTU at setup time of the carrier - needed headroom, when
> adding a vxlan device w/o explicit carrier, then it defaults
> to 1500.
> 
> In case of an explicit carrier that supports jumbo frames, we
> currently cannot change vxlan MTU via ip(8) to > 1500 in
> post-setup time, as vxlan driver uses eth_change_mtu() as default
> method for manually setting MTU.
> 
> Hence, use a custom implementation that only falls back to
> eth_change_mtu() in case we didn't use a dev parameter on device
> setup time, and otherwise allow a max MTU setting of the carrier
> incl. adjustment for headroom.
> 
> Reported-by: Shahed Shaikh <shahed.shaikh@...gic.com>
> Signed-off-by: Daniel Borkmann <dborkman@...hat.com>

Applied, thanks Daniel.
--
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