From: "David S. Miller" <davem@redhat.com>
To: shemminger@osdl.org
Cc: netdev@oss.sgi.com
Subject: Re: Oops on bootup.
Date: Thu, 08 May 2003 10:27:55 -0700 (PDT) [thread overview]
Message-ID: <20030508.102755.25135206.davem@redhat.com> (raw)
In-Reply-To: <20030508112531.0483fccf.shemminger@osdl.org>
From: Stephen Hemminger <shemminger@osdl.org>
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
this point.
I have no idea how your trace is possible besides possible mem
corruption.
prev parent reply other threads:[~2003-05-08 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 18:25 Oops on bootup Stephen Hemminger
2003-05-08 17:27 ` David S. Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030508.102755.25135206.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).