Roland Dreier <rdreier@cisco.com> wrote:

quoted text
> Thanks.  Just to be super-explicit, ioctl() cannot be called on a given
> file until the open() for that particular file has returned, right?

ioctl() will not be called on a given file descriptor before open() is
done, no.  If there are other file descriptors open, though, somebody
can be calling ioctl() on them while the open() for the new one is
executing.
 
quoted text
> And the point about driver initialization is that open() can be called
> as soon as the file operations are registered, even if the module_init
> function has not returned?

That is the point, yes.  The key there is to avoid registering the
device before everything has been set up to actually manage the device. 

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