From: Stephen Hemminger <stephen@networkplumber.org>
To: Jarod Wilson <jarod@redhat.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: Minimum MTU Mess
Date: Wed, 7 Sep 2016 13:35:35 -0700 [thread overview]
Message-ID: <20160907133535.2cfac7bc@xeon-e3> (raw)
In-Reply-To: <20160907195356.GX33916@redhat.com>
On Wed, 7 Sep 2016 15:53:56 -0400
Jarod Wilson <jarod@redhat.com> wrote:
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -6466,9 +6466,17 @@ int dev_set_mtu(struct net_device *dev, int new_mtu)
> if (new_mtu == dev->mtu)
> return 0;
>
> - /* MTU must be positive. */
> - if (new_mtu < 0)
> + if (new_mtu < dev->min_mtu) {
> + netdev_err(dev, "Invalid MTU %d requested, hw min %d\n",
> + new_mtu, dev->min_mtu);
> return -EINVAL;
> + }
> +
> + if (new_mtu > dev->max_mtu) {
> + netdev_err(dev, "Invalid MTU %d requested, hw max %d\n",
> + new_mtu, dev->min_mtu);
> + return -EINVAL;
> + }
>
Maybe don't log something that can be triggered from a user program.
Or at least rate limit it.
next prev parent reply other threads:[~2016-09-07 20:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 17:07 Minimum MTU Mess Jarod Wilson
2016-09-06 16:50 ` [PATCH net-next] sfc: check MTU against minimum threshold Bert Kenward
2016-09-06 21:31 ` Jarod Wilson
2016-09-06 23:54 ` David Miller
2016-09-06 23:55 ` Minimum MTU Mess David Miller
2016-09-07 19:53 ` Jarod Wilson
2016-09-07 20:31 ` Andrew Lunn
2016-09-07 23:43 ` Jarod Wilson
2016-09-08 1:24 ` Andrew Lunn
2016-09-09 18:05 ` Jarod Wilson
2016-09-12 2:41 ` Andrew Lunn
2016-09-12 14:27 ` Jarod Wilson
2016-09-07 20:35 ` Stephen Hemminger [this message]
2016-09-07 23:44 ` Jarod Wilson
2016-09-12 2:59 ` YOSHIFUJI Hideaki
2016-09-12 14:31 ` Jarod Wilson
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=20160907133535.2cfac7bc@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=jarod@redhat.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.