From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] cifs: mark CONFIG_CIFS_NFSD_EXPORT as BROKEN Date: Mon, 23 May 2011 14:23:32 -0400 Message-ID: <20110523182332.GA13791@infradead.org> References: <20110522081707.72cce108@corrin.poochiereds.net> <20110523071208.5dc935f8@corrin.poochiereds.net> <4DDA8BE6.8000001@plainjoe.org> <20110523134542.7d16be6d@tlielax.poochiereds.net> <20110523140722.45c4ffc6@tlielax.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeff Layton , Gerald Carter , Christoph Hellwig , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Steve French Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: On Mon, May 23, 2011 at 01:21:35PM -0500, Steve French wrote: > Until Peter's Linux NFS fix is in - aren't we in that situation > already with other fs. That patch is not going to help with the fundamental problem that you won't be able to ever find an inode that went out of cache. In short cifs in it's current form is fundamentally unsuitable for NFS exporting, and no papering over is going to fix that. Offering it to users is highly dangerous.