From: viro@parcelfarce.linux.theplanet.co.uk
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@redhat.com>
Subject: Re: netlink init order
Date: Sun, 25 May 2003 23:20:06 +0100 [thread overview]
Message-ID: <20030525222005.GK6270@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0305251511140.1741-100000@home.transmeta.com>
On Sun, May 25, 2003 at 03:12:28PM -0700, Linus Torvalds wrote:
>
> On Sun, 25 May 2003 viro@parcelfarce.linux.theplanet.co.uk wrote:
> >
> > BTW, is there any reason why init_netlink_dev() is not a module_init()?
Grr... init_netlink(), that is.
> Probably not. I don't know if the thing even makes sense without a user
> space, which definitely implies that it shouldn't be a "core" initcall.
>
> Even more true as it seems to depend on other core subsystems already
> being initialized.
>
> Davem? Who uses this thing?
After looking at the code in question, I _really_ doubt that other initcalls
might rely on it. It does
* register character device
* create a /dev/netlink (on devfs) and a bunch of entries there.
That's it. Unless we have some initcall code that cares to mount devfs
and open files on it (or does such mknod on rootfs and opens the result)...
next prev parent reply other threads:[~2003-05-25 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 20:27 oops with bk kernel as of 2003-05-25T13:00:00-07 Ulrich Drepper
2003-05-25 21:30 ` viro
2003-05-25 21:51 ` [PATCH] " viro
2003-05-25 22:07 ` netlink init order viro
2003-05-25 22:12 ` Linus Torvalds
2003-05-25 22:20 ` viro [this message]
2003-05-26 2:07 ` David S. Miller
2003-05-26 2:22 ` Linus Torvalds
2003-05-26 2:25 ` David S. Miller
2003-05-26 2:50 ` viro
2003-05-26 2:55 ` David S. Miller
2003-05-26 4:37 ` viro
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=20030525222005.GK6270@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®