From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steven French <sfrench@us.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
akpm@linux-foundation.org, hch@infradead.org,
linux-fsdevel@vger.kernel.org, neilb@suse.de
Subject: Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree
Date: Wed, 16 May 2007 12:02:17 -0400 [thread overview]
Message-ID: <20070516160217.GA9895@fieldses.org> (raw)
In-Reply-To: <OFEBA260F4.E6B7F784-ON872572DD.0051AB8E-862572DD.00520BAB@us.ibm.com>
On Wed, May 16, 2007 at 09:55:41AM -0500, Steven French wrote:
> Any ideas what are the minimum export operation(s) that cifs would need to
> add to export under nfsd? It was not clear to me after reading the
> Exporting document in Documentation directory.
>
> (some users had wanted to export files from Windows servers to nfs clients
> files by putting an nfs server mounted over cifs in between - I realize
> that this can corrupt data due to nfs client caching etc., as even in some
> cases could happen if you try to export a cluster file system under nfsd).
What cases are you thinking of?
--b.
next prev parent reply other threads:[~2007-05-16 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705152152.l4FLqJsV018874@shell0.pdx.osdl.net>
2007-05-16 6:57 ` + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree Christoph Hellwig
2007-05-16 12:53 ` Christoph Hellwig
2007-05-16 14:55 ` Steven French
2007-05-16 16:02 ` J. Bruce Fields [this message]
2007-05-16 17:03 ` Steven French
2007-05-16 21:33 ` J. Bruce Fields
2007-05-17 0:05 ` Neil Brown
2007-05-17 3:11 ` Steven French
2007-05-17 4:26 ` Neil Brown
2007-05-22 9:10 ` Christoph Hellwig
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=20070516160217.GA9895@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sfrench@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).