From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: FS-specified FSID for non-device based filesystems? Date: Thu, 20 Apr 2006 12:35:10 +0100 Message-ID: <20060420113510.GW27946@ftp.linux.org.uk> References: <20060412111003.GZ26989@linuxhacker.ru> <17474.59182.518483.251876@cse.unsw.edu.au> <20060417035043.GA20496@kroah.com> <17475.6724.811707.481414@cse.unsw.edu.au> <20060418180708.GB929@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: greg@kroah.com, neilb@suse.de, green@linuxhacker.ru, linux-fsdevel@vger.kernel.org Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:52638 "EHLO ZenIV.linux.org.uk") by vger.kernel.org with ESMTP id S1750703AbWDTLfP (ORCPT ); Thu, 20 Apr 2006 07:35:15 -0400 To: Miklos Szeredi Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Apr 19, 2006 at 02:15:41PM +0200, Miklos Szeredi wrote: > > > because Al Viro pokes obvious holes in the scheme. > > > > > > I cannot find anything in Documentation/filesystems/sysfs.txt, so: > > > How is /sys/fs supposed to work? > > > > I don't know, as I didn't create it. I think one of the FUSE developers > > did. > > Yeah. There are a couple of FUSE specific attributes under > /sys/fs/fuse (documented in Documentation/filesystems/fuse.txt). > > I'll put a pointer into sysfs.txt. Speaking of obvious holes, what is /* Setting file->private_data can't race with other mount() instances, since BKL is held for ->get_sb() */ if (file->private_data) return -EINVAL; doing, seeing that the next thing you do is GFP_KERNEL allocations, which would kill all hope to use BKL-based protection here?