From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: 2.6.8.1-mm2 Date: Thu, 19 Aug 2004 10:43:42 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040819104342.A7641@infradead.org> References: <20040819014204.2d412e9b.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, viro@parcelfarce.linux.theplanet.co.uk Return-path: Received: from imladris.demon.co.uk ([193.237.130.41]:13063 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S264503AbUHSJnp (ORCPT ); Thu, 19 Aug 2004 05:43:45 -0400 To: Andrew Morton , reiser@namesys.com Content-Disposition: inline In-Reply-To: <20040819014204.2d412e9b.akpm@osdl.org>; from akpm@osdl.org on Thu, Aug 19, 2004 at 01:42:04AM -0700 List-Id: linux-fsdevel.vger.kernel.org > +reiser4-allow-drop_inode-implementation.patch > +reiser4-allow-drop_inode-implementation-cleanup.patch Please don't do this. The only reason reiser4 needs that is because their broken internal plugin scheme that can't distinguish ->rmdir and ->unlink forces them to reimplement the generic code inside the fs driver. It's not the kind of functions we want exported. > +reiser4-export-inode_lock.patch > +reiser4-export-inode_lock-cleanup.patch Similarly inode_lock is nothing that should be exported to drivers, it's too much of an internal that can change - and something drivers can really badly screw up on.