Re: udev is too slow creating devices

[Alexander E. Patrakov]

Marc Ballarin wrote:
> On Sun, 19 Sep 2004 16:25:51 +0200
> Ihar 'Philips' Filipau <filia@xxxxxxxxxxxx> wrote:
>
>
> >   Well, can then anyone explain by which mean (black magic?) kernel 
> > mounts root file system? block device might appear any time, file system
> > might take ages to load.
>
>
> The kernel doesn't use /dev.

It creates a temporary device node in its rootfs. It does so by looking 
into sysfs for major and minor numbers. So the question is whether the 
information is in sysfs at the moment when the kernel requests it.

> Why do you think mounting the root device is such a "frail" process?

Because of your own words below that "loading the driver might fail at 
any point *after* modprobe returns" (read: after module_init() finishes).

> The kernel blindly ties all known filesystem on the specified device.

yes, if it exists

> If the user specifies a wrong root device, or the device is broken or the
> filesystem corrupted or unknown the kernel will panic.
> The reason this is so is, that nothing else can be done. Userspace,
> however, has more possibilities.

OK. The fact is that, when mounting the root filesystem, the kernel can 
(?) definitely say "there is no such device, and it's useless to wait 
for it--so I panic". Is it possible to duplicate this logic in the case 
with udev and modprobe? If so, it should be built into a common place 
(either the kernel or into modprobe), but not into all apps.


> Instead of:
> modprobe ide-cd && mount /dev/hdc /mnt/cdrom
> in /etc/init.d/your-script
>
> you would now do:
> if [ ACTION="add" ] && [ DEVNAME="/dev/hdc" ]; then
> 	mount /dev/hdc /mnt/cdrom
> fi
> in /etc/dev.d/default/your-script.dev
>
> This is even more reliable than the first solution on a static /dev,
> since loading the driver might fail at any point *after* modprobe
> returns.
> For example, modprobe ide-cd will succeed even when no CD-ROMs are
> present. The old script would break in this case, the new one wouldn't be
> called at all.
<snip>
> You just have to adopt your approach to device handling. Currently you
> *assume* that after a succesfull modprobe the device nodes are available
> (this was never true, however).

Then the "char-major" aliases were always broken, do I understand 
correctly? Once we realize that, isn't it the time to mark the 
"Automatic kernel module loading" in the kernel configuration as BROKEN 
or OBSOLETE?

> With hotplug/udev you *know* that the device node is available when your
> script in dev.d is called with the appropriate environment variables.

Yes. Now we have a lot of short scriptlets under /etc/dev.d. But I don't 
yet see how these scriptlets interact with each other.

--
Alexander E. Patrakov

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/