Messages in this thread | | | Date | Tue, 20 May 2008 09:26:51 +0100 | From | Alan Cox <> | Subject | Re: [PATCH, RFC] Char dev BKL pushdown v2 |
| |
> Thanks. Just to be super-explicit, ioctl() cannot be called on a given > file until the open() for that particular file has returned, right?
Right. Or two ioctls against each other unless one sleepers, or against random other parts of the kernel which still use the BKL - eg fasync, bits of procfs ...
> 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?
Exactly.
Alan
| |