Messages in this thread | | | From | Roland Dreier <> | Subject | Re: [PATCH, RFC] Char dev BKL pushdown v2 | Date | Mon, 19 May 2008 15:18:06 -0700 |
| |
> That's part of it, but, as Alan pointed out, there's more. The BKL > currently protects open() calls against concurrency with other opens, > with ioctl(), and with driver initialization as well. So it's a matter > of having one's locking and ordering act together in general.
Thanks. Just to be super-explicit, ioctl() cannot be called on a given file until the open() for that particular file has returned, right?
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?
Thanks, Roland
| |