netdev - Re: [PATCH net-next] r8169: don't set min_mtu/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]

Message-Id: <20200127.111608.325265803073380152.davem@davemloft.net>
Date:   Mon, 27 Jan 2020 11:16:08 +0100 (CET)
From:   David Miller <davem@...emloft.net>
To:     hkallweit1@...il.com
Cc:     nic_swsd@...ltek.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] r8169: don't set min_mtu/max_mtu if not needed

From: Heiner Kallweit <hkallweit1@...il.com>
Date: Sun, 26 Jan 2020 10:40:44 +0100

> Defaults for min_mtu and max_mtu are set by ether_setup(), which is
> called from devm_alloc_etherdev(). Let rtl_jumbo_max() only return
> a positive value if actually jumbo packets are supported. This also
> allows to remove constant Jumbo_1K which is a little misleading anyway.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@...il.com>

Applied, thank you.