Re: [PATCH, RFC] Char dev BKL pushdown v2

From: Roland Dreier
Date: Mon May 19 2008 - 18:19:46 EST

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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at