Roland Dreier <rdreier@cisco.com> wrote:

quoted text
> OK, will send such a patch after auditing more carefully.  Just to be
> very clear, the issue is to make sure the locking is sufficient to
> protect against multiple racing open calls to the same character device?

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.

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/