diff options
author | Jarod Wilson <jarod@redhat.com> | 2015-11-03 23:09:32 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-11-04 21:56:00 -0500 |
commit | e7868a85e1b26bcb2e71088841eec1d310a97ac9 (patch) | |
tree | f6b665fe149ff637ff201313ec9ef44e2480aa1b /lib/atomic64_test.c | |
parent | e1b8d903c6c3862160d2d5036806a94786c8fc4e (diff) | |
download | linux-e7868a85e1b26bcb2e71088841eec1d310a97ac9.tar.bz2 |
net/core: ensure features get disabled on new lower devs
With moving netdev_sync_lower_features() after the .ndo_set_features
calls, I neglected to verify that devices added *after* a flag had been
disabled on an upper device were properly added with that flag disabled as
well. This currently happens, because we exit __netdev_update_features()
when we see dev->features == features for the upper dev. We can retain the
optimization of leaving without calling .ndo_set_features with a bit of
tweaking and a goto here.
Fixes: fd867d51f889 ("net/core: generic support for disabling netdev features down stack")
CC: "David S. Miller" <davem@davemloft.net>
CC: Eric Dumazet <edumazet@google.com>
CC: Jay Vosburgh <j.vosburgh@gmail.com>
CC: Veaceslav Falico <vfalico@gmail.com>
CC: Andy Gospodarek <gospo@cumulusnetworks.com>
CC: Jiri Pirko <jiri@resnulli.us>
CC: Nikolay Aleksandrov <razor@blackwall.org>
CC: Michal Kubecek <mkubecek@suse.cz>
CC: Alexander Duyck <alexander.duyck@gmail.com>
CC: netdev@vger.kernel.org
Reported-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib/atomic64_test.c')
0 files changed, 0 insertions, 0 deletions