From: Al Viro <viro@ftp.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: greg@kroah.com, neilb@suse.de, green@linuxhacker.ru,
linux-fsdevel@vger.kernel.org
Subject: Re: FS-specified FSID for non-device based filesystems?
Date: Thu, 20 Apr 2006 12:35:10 +0100 [thread overview]
Message-ID: <20060420113510.GW27946@ftp.linux.org.uk> (raw)
In-Reply-To: <E1FWBav-0002Jy-00@dorka.pomaz.szeredi.hu>
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?
next prev parent reply other threads:[~2006-04-20 11:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 11:10 FS-specified FSID for non-device based filesystems? Oleg Drokin
2006-04-14 20:22 ` Bryan Henderson
2006-04-14 20:45 ` Oleg Drokin
2006-04-14 20:59 ` J. Bruce Fields
2006-04-14 21:32 ` Bryan Henderson
2006-04-14 21:41 ` Oleg Drokin
2006-04-17 0:54 ` Neil Brown
2006-04-17 3:50 ` Greg KH
2006-04-17 4:32 ` Neil Brown
2006-04-18 18:07 ` Greg KH
2006-04-19 12:15 ` Miklos Szeredi
2006-04-20 11:35 ` Al Viro [this message]
2006-04-20 11:58 ` Miklos Szeredi
2006-04-20 12:30 ` Al Viro
2006-04-20 12:43 ` Miklos Szeredi
2006-04-17 8:00 ` Anton Altaparmakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060420113510.GW27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=green@linuxhacker.ru \
--cc=greg@kroah.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.