[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121203142229.GA3054@minipsycho.orion>
Date: Mon, 3 Dec 2012 15:22:29 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Neil Horman <nhorman@...driver.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
bhutchings@...arflare.com, psimerda@...hat.com
Subject: Re: [patch net-next] net: call notifiers for mtu change even if
iface is not up
Mon, Dec 03, 2012 at 03:18:23PM CET, nhorman@...driver.com wrote:
>On Mon, Dec 03, 2012 at 12:16:32PM +0100, Jiri Pirko wrote:
>> Do the same thing as in set mac. Call notifiers every time.
>>
>> Signed-off-by: Jiri Pirko <jiri@...nulli.us>
>> ---
>> net/core/dev.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/core/dev.c b/net/core/dev.c
>> index 2f94df2..0685a72 100644
>> --- a/net/core/dev.c
>> +++ b/net/core/dev.c
>> @@ -4971,7 +4971,7 @@ int dev_set_mtu(struct net_device *dev, int new_mtu)
>> else
>> dev->mtu = new_mtu;
>>
>> - if (!err && dev->flags & IFF_UP)
>> + if (!err)
>> call_netdevice_notifiers(NETDEV_CHANGEMTU, dev);
>> return err;
>> }
>
>I'm not opposed to this change, but is there something that it expressly fixes?
This is about a consistency. To have the same behaviour as set_mac
for example.
>While it doesn't hurt to send around mtu change events, one would presume that
>listeners would pick up mtu changes when the NETDEV_UP event went' around.
>
>Neil
>
>--
>To unsubscribe from this list: send the line "unsubscribe netdev" in
>the body of a message to majordomo@...r.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists