From: "David S. Miller" <davem@redhat.com>
To: sopwith@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: knfsd and FS_REQUIRES_DEV
Date: Tue, 11 Dec 2001 16:20:11 -0800 (PST) [thread overview]
Message-ID: <20011211.162011.21927662.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112111810160.541-100000@devserv.devel.redhat.com>
In-Reply-To: <Pine.LNX.4.33.0112111810160.541-100000@devserv.devel.redhat.com>
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.
next prev parent reply other threads:[~2001-12-12 0:20 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 [this message]
2001-12-12 0:45 ` Elliot Lee
2001-12-12 1:21 ` Neil Brown
2001-12-12 0:46 ` Linus Torvalds
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=20011211.162011.21927662.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sopwith@redhat.com \
/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.