aboutsummaryrefslogtreecommitdiffstats
path: root/lib/kstrtox.c
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2011-10-24 21:25:21 +0000
committerGreg Kroah-Hartman <gregkh@suse.de>2011-11-11 09:35:47 -0800
commit5c2433cdc72a03446184e2f898be3b05095b5ed0 (patch)
treeb4532445ad6d2b5ceaf9eb44409580b97effecb4 /lib/kstrtox.c
parent7b59e3e29e1a28ad40892dd2115175e2702f1153 (diff)
downloadkernel_samsung_smdk4412-5c2433cdc72a03446184e2f898be3b05095b5ed0.zip
kernel_samsung_smdk4412-5c2433cdc72a03446184e2f898be3b05095b5ed0.tar.gz
kernel_samsung_smdk4412-5c2433cdc72a03446184e2f898be3b05095b5ed0.tar.bz2
caif: Fix BUG() with network namespaces
commit 08613e4626c06ca408fc55071f6aedee36986a87 upstream. The caif code will register its own pernet_operations, and then register a netdevice_notifier. Each time the netdevice_notifier is triggered, it'll do some stuff... including a lookup of its own pernet stuff with net_generic(). If the net_generic() call ever returns NULL, the caif code will BUG(). That doesn't seem *so* unreasonable, I suppose — it does seem like it should never happen. However, it *does* happen. When we clone a network namespace, setup_net() runs through all the pernet_operations one at a time. It gets to loopback before it gets to caif. And loopback_net_init() registers a netdevice... while caif hasn't been initialised. So the caif netdevice notifier triggers, and immediately goes BUG(). We could imagine a complex and overengineered solution to this generic class of problems, but this patch takes the simple approach. It just makes caif_device_notify() *not* go looking for its pernet data structures if the device it's being notified about isn't a caif device in the first place. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> Acked-by: Sjur Brændeland <sjur.brandeland@stericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'lib/kstrtox.c')
0 files changed, 0 insertions, 0 deletions