From: David Miller <davem@davemloft.net>
To: jarod@redhat.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
asbjorn@asbjorn.st, parameswaran.r7@gmail.com
Subject: Re: [PATCH net] net: remove MTU limits on a few ether_setup callers
Date: Fri, 21 Oct 2016 13:58:28 -0400 (EDT) [thread overview]
Message-ID: <20161021.135828.966455231750113733.davem@davemloft.net> (raw)
In-Reply-To: <20161021032527.12954-1-jarod@redhat.com>
From: Jarod Wilson <jarod@redhat.com>
Date: Thu, 20 Oct 2016 23:25:27 -0400
> These few drivers call ether_setup(), but have no ndo_change_mtu, and thus
> were overlooked for changes to MTU range checking behavior. They
> previously had no range checks, so for feature-parity, set their min_mtu
> to 0 and max_mtu to ETH_MAX_MTU (65535), instead of the 68 and 1500
> inherited from the ether_setup() changes. Fine-tuning can come after we get
> back to full feature-parity here.
>
> CC: netdev@vger.kernel.org
> Reported-by: Asbjoern Sloth Toennesen <asbjorn@asbjorn.st>
> CC: Asbjoern Sloth Toennesen <asbjorn@asbjorn.st>
> CC: R Parameswaran <parameswaran.r7@gmail.com>
> Signed-off-by: Jarod Wilson <jarod@redhat.com>
Applied.
Please use "[PATCH net-next]" in your subject line when a patch
targets net-next.
prev parent reply other threads:[~2016-10-21 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 3:25 [PATCH net] net: remove MTU limits on a few ether_setup callers Jarod Wilson
2016-10-21 3:42 ` Florian Fainelli
2016-10-21 8:44 ` Andrew Lunn
2016-10-21 15:48 ` Jarod Wilson
2016-10-21 15:59 ` Andrew Lunn
2016-10-21 17:58 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161021.135828.966455231750113733.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=asbjorn@asbjorn.st \
--cc=jarod@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parameswaran.r7@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).