public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: knfsd and FS_REQUIRES_DEV
Date: Wed, 12 Dec 2001 00:46:10 +0000 (UTC)	[thread overview]
Message-ID: <9v69ci$5e1$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112111810160.541-100000@devserv.devel.redhat.com> <20011211.162011.21927662.davem@redhat.com>

In article <20011211.162011.21927662.davem@redhat.com>,
David S. Miller <davem@redhat.com> wrote:
>   From: Elliot Lee <sopwith@redhat.com>
>   Date: Tue, 11 Dec 2001 19:13:48 -0500 (EST)
>
>   I'm looking for information on knfsd's requirement that a filesystem be
>   FS_REQUIRES_DEV in order to export it. Would someone point me in the right
>   direction?
>   
>   Needing to implement some not-quite-kosher exports,
>
>NFSD puts dev/ino into the filehandles it gives to the
>client, it uses this to lookup the inode in question.

Well, that actually could work with things like /proc, which actually
has meaningful inode numbers. They may not be stable across reboots, of
course, nor even really stable in general, but in _theory_ there's
nothing to keep us from exporting /proc files and potentially other
virtual filesystems.

In practice I suspect there are tons of other problems, not the least of
which is that /proc doesn't give a proper filesize. 

Other not-so-kosher filesystems (ie tmpfs) might be easier than /proc in
those respects. 

		Linus

  parent reply	other threads:[~2001-12-12  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12  0:13 knfsd and FS_REQUIRES_DEV Elliot Lee
2001-12-12  0:20 ` David S. Miller
2001-12-12  0:45   ` Elliot Lee
2001-12-12  1:21     ` Neil Brown
2001-12-12  0:46   ` Linus Torvalds [this message]
2001-12-12  2:15     ` Trond Myklebust

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='9v69ci$5e1$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox