Re: [PATCH net-next] ipv4: do not abuse GFP_ATOMIC in inet_netconf_notify_devconf()

2016-07-09 Thread David Miller
From: Eric Dumazet Date: Fri, 08 Jul 2016 05:18:24 +0200 > From: Eric Dumazet > > inet_forward_change() runs with RTNL held. > We are allowed to sleep if required. > > If we use __in_dev_get_rtnl() instead of __in_dev_get_rcu(), > we no longer have to use GFP_ATOMIC allocations in > inet_netco

Re: [PATCH net-next] ipv4: do not abuse GFP_ATOMIC in inet_netconf_notify_devconf()

2016-07-08 Thread Nicolas Dichtel
Le 08/07/2016 05:18, Eric Dumazet a écrit : > From: Eric Dumazet > > inet_forward_change() runs with RTNL held. > We are allowed to sleep if required. > > If we use __in_dev_get_rtnl() instead of __in_dev_get_rcu(), > we no longer have to use GFP_ATOMIC allocations in > inet_netconf_notify_devco

[PATCH net-next] ipv4: do not abuse GFP_ATOMIC in inet_netconf_notify_devconf()

2016-07-07 Thread Eric Dumazet
From: Eric Dumazet inet_forward_change() runs with RTNL held. We are allowed to sleep if required. If we use __in_dev_get_rtnl() instead of __in_dev_get_rcu(), we no longer have to use GFP_ATOMIC allocations in inet_netconf_notify_devconf(), meaning we are less likely to miss notifications under