Re: [2.6 PATCH/RFC] Firmware loader - fix races and resourcedealloocation problems

[Marcel Holtmann]

Hi Dmitry,

> > > It seems that implementation of the firmware loader is racy as it
> > > relies on kobject hotplug handler. Unfortunately that handler runs
> > > too early, before firmware class attributes controlling the loading
> > > process, are created. This causes firmware loading fail at least half
> > > of the times on my laptop.
> >
> > Um, why not have your script wait until the files are present?  That
> > will remove any race conditions you will have.
> 
> How long should the userspace wait? One second as Manuel suggested?
> Indefinitely? Or should the firmware agent have some timeout? If userspace
> uses a timeout how should it correlate with the timeout on the kernel side?

the timeout of the kernel (which can be set from userspace) is for the
whole firmware loading process. What we talk about is waiting a little
bit before the files become visible for the firmware.agent.

> I am sorry but I have to disagree with you. Kernel should not call user
> space until it has all infrastructure in place and is ready. Anything
> else is just a sloppy practice.

The firmware.agent script has 3 extra lines to check for the visibility
of the "loading" file and if it is not present it will sleep one second.
This is a actual good practice compared to adding much more code to the
kernel and have an own way of running hotplug.

Regards

Marcel


-
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/