From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anton Altaparmakov Subject: Re: NFS4 crack Date: Mon, 19 Sep 2005 14:04:03 +0100 Message-ID: <1127135043.493.19.camel@imp.csi.cam.ac.uk> References: <20050918102100.GA23463@lst.de> <20050918143615.GA3428@fieldses.org> <20050919103547.GA8998@lst.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: "J. Bruce Fields" , akpm@osdl.org, neilb@cse.unsw.edu.au, andros@citi.umich.edu, linux-fsdevel@vger.kernel.org Return-path: Received: from ppsw-0.csi.cam.ac.uk ([131.111.8.130]:63725 "EHLO ppsw-0.csi.cam.ac.uk") by vger.kernel.org with ESMTP id S932295AbVISNEe (ORCPT ); Mon, 19 Sep 2005 09:04:34 -0400 To: Christoph Hellwig In-Reply-To: <20050919103547.GA8998@lst.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 2005-09-19 at 12:35 +0200, Christoph Hellwig wrote: > On Sun, Sep 18, 2005 at 10:36:15AM -0400, J. Bruce Fields wrote: > > On Sun, Sep 18, 2005 at 12:21:00PM +0200, Christoph Hellwig wrote: [snip] > > > The fs handling in fs/nfs/nfs4recovery.c is rather broken in addition. > > > > For example? [snip] > - tries to build dentry list from vfs_readdir callback, leading to > deadlocks on filesystems that take the same lock from readdir > and lookup NFSv3 has always done this and yes it did lead to deadlock in ntfs so I had to work around it in ntfs to get it to work. I had to redesign how the locking worked which was really annoying thing to have to do. )-: Just pointing this out as it seems to be commonplace for nfs and nothing new... Best regards, Anton -- Anton Altaparmakov (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/