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

From: Ingo Molnar
Date: Mon May 19 2008 - 09:24:33 EST

* Jonathan Corbet <corbet@xxxxxxx> wrote:

> OK, since the previous announcement, I've revisited all of the open()
> functions which didn't get lock_kernel() calls the first time around.
> Alan pointed out that even a completely empty open() might, in fact,
> need to acquire the BKL, so now they all do. Hopefully, this
> completes this work (at this level - there's plenty of down-pushing to
> do within subsystems).

cool stuff! :-)

> There's a new tree with this stuff:
> git:// bkl-removal
> Stephen, might it be about time to pull this into linux-next and see
> what explodes?
> If others have BKL-removal patches which look like 2.6.27 material,
> I'll happily collect them in this tree.

i'm wondering how this should best interact with the kill-the-BKL bits
that attack it all from the infrastructure side. Your bits are the safer
ones, so i guess i'll try to track your changes from my branch to
increase testing of it all?

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