Prev: [132/165] ext4: Make fsync sync new parent directories in no-journal mode
Next: [129/165] ext4: restart ext4_ext_remove_space() after transaction restart
From: Jesper Nilsson on 30 Jul 2010 13:30
On Sun, Jul 11, 2010 at 11:18:58PM +0200, Arnd Bergmann wrote:
> 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.

Thanks, added to the cris-tree.

/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson(a)axis.com
--
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: [132/165] ext4: Make fsync sync new parent directories in no-journal mode
Next: [129/165] ext4: restart ext4_ext_remove_space() after transaction restart