Prev: tip/master broken with x2apic and kexec
Next: net: autoconvert trivial BKL users to private mutex
From: David Miller on 12 Jul 2010 23:40
From: Arnd Bergmann <arnd(a)arndb.de>
Date: Sun, 11 Jul 2010 23:18:53 +0200

> All these files use the big kernel lock in a trivial
> way to serialize their private file operations,
> typically resulting from an earlier semi-automatic
> pushdown from VFS.
>
> None of these drivers appears to want to lock against
> other code, and they all use the BKL as the top-level
> lock in their file operations, meaning that there
> is no lock-order inversion problem.
>
> Consequently, we can remove the BKL completely,
> replacing it with a per-file mutex in every case.
> Using a scripted approach means we can avoid
> typos.
....
> Signed-off-by: Arnd Bergmann <arnd(a)arndb.de>

Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: tip/master broken with x2apic and kexec
Next: net: autoconvert trivial BKL users to private mutex