From: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Thu, 8 May 2003 11:25:31 -0700
This happened once and is not reproducible.
There appears to be initialization window where netlink data can
arrive before socket slab cache is initialized or something like that.
Probably a packet has to arrive at just the right time or something similar.
It's oopsing on sock_inode_cachep. We init that in sock_init()
which is invoked explicitly by do_basic_setup().
The calltrace is back into netlink_kernel_create via rtnetlink_init
via netlink_proto_init. netlink_proto_init was recently changed
into a subsys initcall.
Because it is a subsys initcall, it must be invoked after sock_init()
and therefore the sock_inode_cachep must be initialized properly at
I have no idea how your trace is possible besides possible mem