[v2] Remaining BKL users, what to do
arnd at arndb.de
Mon Oct 18 10:38:26 PDT 2010
On Monday 18 October 2010 18:19:24 Christoph Hellwig wrote:
> Before we get into all these fringe drivers:
> - I've not seen any progrss on ->get_sb BKL removal for a while
Not sure what you mean. Jan Blunck did the pushdown into get_sb
last year, which is included into linux-next through my bkl/vfs
tree. Subsequent patches remove it from most file systems along with
the other BKL uses in them. If you like, I can post the series
once more, but it has been posted a few times now.
> - locks.c is probably a higher priorit, too.
As mentioned in the list, I expect the trivial final patch to
be applied in 2.6.37-rc1 after Linus has pulled the trees that
this depends on (bkl/vfs, nfs, nfsd, ceph), see below.
This is currently not in -next because of the prerequisites.
diff --git a/fs/Kconfig b/fs/Kconfig
index c386a9f..25ce2dc 100644
@@ -50,7 +50,6 @@ endif # BLOCK
bool "Enable POSIX file locking API" if EMBEDDED
- select BKL
This option enables standard file locking support, required
for filesystems like NFS and for the flock() system
diff --git a/fs/locks.c b/fs/locks.c
index 8b2b6ad..02b6e0e 100644
@@ -142,6 +142,7 @@ int lease_break_time = 45;
* Protects the two list heads above, plus the inode->i_flock list
@@ -149,13 +150,13 @@ static LIST_HEAD(blocked_list);
More information about the dri-devel