netdev - Re: [PATCH next] ipvlan: inherit MTU from master device

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]

Date:	Thu, 04 Feb 2016 19:22:21 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	mahesh@...dewar.net
Cc:	maheshb@...gle.com, edumazet@...gle.com, thockin@...gle.com,
	netdev@...r.kernel.org, eric.dumazet@...il.com, thockins@...gle.com
Subject: Re: [PATCH next] ipvlan: inherit MTU from master device

From: Mahesh Bandewar <mahesh@...dewar.net>
Date: Wed, 27 Jan 2016 23:33:28 -0800

> From: Mahesh Bandewar <maheshb@...gle.com>
> 
> When we create IPvlan slave; we use ether_setup() and that
> sets up default MTU to 1500 while the master device may have
> lower / different MTU. Any subsequent changes to the masters'
> MTU are reflected into the slaves' MTU setting. However if those
> don't happen (most likely scenario), the slaves' MTU stays at
> 1500 which could be bad.
> 
> This change adds code to inherit MTU from the master device
> instead of using the default value during the link initialization
> phase.
> 
> Signed-off-by: Mahesh Bandewar <maheshb@...gle.com>

Applied, thanks.