From: Alexander Duyck <alexander.h.duyck@intel•com>
To: Veaceslav Falico <vfalico@redhat•com>, netdev@vger•kernel.org
Cc: Jiri Pirko <jiri@resnulli•us>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Nicolas Dichtel <nicolas.dichtel@6wind•com>
Subject: Re: [PATCH net-next] net: make dev_set_mtu() honor notification return code
Date: Fri, 10 Jan 2014 07:36:45 -0800 [thread overview]
Message-ID: <52D0138D.6050302@intel.com> (raw)
In-Reply-To: <1389358097-5396-1-git-send-email-vfalico@redhat.com>
On 01/10/2014 04:48 AM, Veaceslav Falico wrote:
> Currently, after changing the MTU for a device, dev_set_mtu() calls
> NETDEV_CHANGEMTU notification, however doesn't verify it's return code -
> which can be NOTIFY_BAD - i.e. some of the net notifier blocks refused this
> change, and continues nevertheless.
>
> To fix this, verify the return code, and if it's an error - then revert the
> MTU to the original one, and pass the error code.
>
> CC: Jiri Pirko <jiri@resnulli•us>
> CC: "David S. Miller" <davem@davemloft•net>
> CC: Eric Dumazet <edumazet@google•com>
> CC: Alexander Duyck <alexander.h.duyck@intel•com>
> CC: Nicolas Dichtel <nicolas.dichtel@6wind•com>
> Signed-off-by: Veaceslav Falico <vfalico@redhat•com>
> ---
> net/core/dev.c | 29 ++++++++++++++++++++---------
> 1 file changed, 20 insertions(+), 9 deletions(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index ce01847..1c570ff 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -5287,6 +5287,17 @@ int dev_change_flags(struct net_device *dev, unsigned int flags)
> }
> EXPORT_SYMBOL(dev_change_flags);
>
> +static int __dev_set_mtu(struct net_device *dev, int new_mtu)
> +{
> + const struct net_device_ops *ops = dev->netdev_ops;
> +
> + if (ops->ndo_change_mtu)
> + return ops->ndo_change_mtu(dev, new_mtu);
> +
> + dev->mtu = new_mtu;
> + return 0;
> +}
> +
> /**
> * dev_set_mtu - Change maximum transfer unit
> * @dev: device
> @@ -5296,8 +5307,7 @@ EXPORT_SYMBOL(dev_change_flags);
> */
> int dev_set_mtu(struct net_device *dev, int new_mtu)
> {
> - const struct net_device_ops *ops = dev->netdev_ops;
> - int err;
> + int err, orig_mtu;
>
> if (new_mtu == dev->mtu)
> return 0;
> @@ -5309,14 +5319,15 @@ int dev_set_mtu(struct net_device *dev, int new_mtu)
> if (!netif_device_present(dev))
> return -ENODEV;
>
> - err = 0;
> - if (ops->ndo_change_mtu)
> - err = ops->ndo_change_mtu(dev, new_mtu);
> - else
> - dev->mtu = new_mtu;
> + orig_mtu = dev->mtu;
> + err = __dev_set_mtu(dev, new_mtu);
>
> - if (!err)
> - call_netdevice_notifiers(NETDEV_CHANGEMTU, dev);
> + if (!err) {
> + err = call_netdevice_notifiers(NETDEV_CHANGEMTU, dev);
> + err = notifier_to_errno(err);
> + if (err)
> + __dev_set_mtu(dev, orig_mtu);
> + }
> return err;
> }
> EXPORT_SYMBOL(dev_set_mtu);
So what about the netdevices that succeeded in changing the MTU based on
the notifiers? It seems like you still have an inconsistent state
after the failure unless you issue a second call with a notification
that you reverted to the old MTU.
Thanks,
Alex
next prev parent reply other threads:[~2014-01-10 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 12:48 [PATCH net-next] net: make dev_set_mtu() honor notification return code Veaceslav Falico
2014-01-10 15:36 ` Alexander Duyck [this message]
2014-01-10 15:47 ` Veaceslav Falico
2014-01-13 23:18 ` David Miller
2014-01-14 12:13 ` Veaceslav Falico
2014-01-15 21:48 ` David Miller
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=52D0138D.6050302@intel.com \
--to=alexander.h.duyck@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nicolas.dichtel@6wind$(echo .)com \
--cc=vfalico@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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