From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree Date: Wed, 16 May 2007 12:02:17 -0400 Message-ID: <20070516160217.GA9895@fieldses.org> References: <20070516065721.GA9884@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , akpm@linux-foundation.org, hch@infradead.org, linux-fsdevel@vger.kernel.org, neilb@suse.de To: Steven French Return-path: Received: from mail.fieldses.org ([66.93.2.214]:33660 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755943AbXEPQDz (ORCPT ); Wed, 16 May 2007 12:03:55 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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.