On Wed, 2010-04-14 at 22:36 +0200, Arnd Bergmann wrote: > From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx> > > I've taken a patch originally written by Matthew Wilcox and > ported it to the current version. It seems that there were > originally concerns that this breaks NFS, but since Trond > has recently removed the BKL from NFS, my naive assumption > would be that it's all good now, despite not having tried to > understand what it does. Hi Arnd, We still need to fix up the bits in NFS that dereference inode->i_flock. On the client side, those are mainly the bits that deal with lock recovery when the NFS server has rebooted or restarted. AFAICS, there are two places in the NFSv4 client that need to be changed to call lock_flocks(): nfs_delegation_claim_locks(), and nfs4_reclaim_locks(). In both cases, the replacement is trivial. For NFSv3, I think we are already safe, since AFAICS the host->h_rwsem already provides exclusion between file locking and lock recovery attempts. I think we should therefore be able to immediately remove the BKL in fs/lockd/clntlock.c:reclaimer(). I'm not as sure about how sensitive the NFS server is to the switch from BKL -> lock_flocks(). Perhaps Bruce can comment... Cheers Trond -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
