From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction) Date: Fri, 15 Dec 2006 08:05:24 -0500 Message-ID: <45829D94.1090304@redhat.com> References: <457891E7.10902@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Return-path: Received: from mx1.redhat.com ([66.187.233.31]:38028 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752100AbWLONFg (ORCPT ); Fri, 15 Dec 2006 08:05:36 -0500 To: akpm@osdl.org In-Reply-To: <457891E7.10902@redhat.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Jeff Layton wrote: > Apologies for the long email, but I couldn't come up with a way to explain > this in fewer words. Many filesystems that are part of the linux kernel > have problems with how they have assign out i_ino values: > If there are no further comments/suggestions on this patchset, I'd like to ask Andrew to add it to -mm soon and target getting it rolled into 2.6.21. Once it's in -mm, I'll start posting more patches to convert the other filesystems. Andrew, are the patches I've already posted sufficient, or should I resend the set? Thanks, Jeff