Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758856AbYHOWxP (ORCPT ); Fri, 15 Aug 2008 18:53:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752222AbYHOWw5 (ORCPT ); Fri, 15 Aug 2008 18:52:57 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:46727 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752121AbYHOWw5 (ORCPT ); Fri, 15 Aug 2008 18:52:57 -0400 Date: Fri, 15 Aug 2008 15:52:20 -0700 From: Andrew Morton To: Atsushi Nemoto Cc: viro@ZenIV.linux.org.uk, djohnson@sw.starentnetworks.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, stable@kernel.org Subject: Re: cramfs and named-pipe Message-Id: <20080815155220.91ec8201.akpm@linux-foundation.org> In-Reply-To: <20080805.120909.139657748.nemoto@toshiba-tops.co.jp> References: <20080804.182143.218269280.nemoto@toshiba-tops.co.jp> <20080804100347.GU28946@ZenIV.linux.org.uk> <20080805.120909.139657748.nemoto@toshiba-tops.co.jp> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1358 Lines: 30 On Tue, 05 Aug 2008 12:09:09 +0900 (JST) Atsushi Nemoto wrote: > On Mon, 4 Aug 2008 11:03:47 +0100, Al Viro wrote: > > Eeek... I'd rather not play these games with directories and devices nodes > > as well. Rationale for the original patch simply doesn't apply for those. > > > > IOW, I think it would be much saner if we did the following: make ..._test() > > refuse to merge inodes with ->i_ino == 1, take inode setup back to > > get_cramfs_inode() and make ->drop_inode() evict ones with ->i_ino == 1 > > immediately. Comments? > > > > Patch below is completely untested; it builds, but that's it. > > Thanks, your patch works well for me. But it looks a bit large for > stable tree (100 line rule). > > With current code, I think no problem on empty directories and device > nodes. So how about fixing only FIFO case first (and send it to > stable tree) and then go to your patch? > Nothing seems to have happened. Al, do you think your (now tested) patch is good for 2.6.27 and 2.6.26.x? And, it seems, 2.6.25.x. (All the way down to 2.6.14.x!) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/