From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Wedgwood <cw@f00f.org>
Subject: Re: 64-bit inode number issues
Date: Mon, 16 Oct 2006 23:02:54 -0700
Message-ID: <20061017060254.GA30598@tuatara.stupidest.org>
References: <20060928164529.GA3497@infradead.org> <13246.1159971501@warthog.cambridge.redhat.com> <20061007210131.GA17717@infradead.org> <20061012183232.GG4141@kvack.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Christoph Hellwig <hch@infradead.org>,
	David Howells <dhowells@redhat.com>, aviro@redhat.com,
	akpm@osdl.org, linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from smtp113.sbc.mail.mud.yahoo.com ([68.142.198.212]:14203 "HELO
	smtp113.sbc.mail.mud.yahoo.com") by vger.kernel.org with SMTP
	id S1423129AbWJQGC6 (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 17 Oct 2006 02:02:58 -0400
To: Benjamin LaHaise <bcrl@kvack.org>
Content-Disposition: inline
In-Reply-To: <20061012183232.GG4141@kvack.org>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Thu, Oct 12, 2006 at 02:32:32PM -0400, Benjamin LaHaise wrote:

> The only real way to get any exercising of the relevant code paths
> would be to fake 64 bit inode numbers in a commonly used filesystem
> like ext3.

Why not add a config option (or boot-time flash) or even mount option
to have *existing* inode numbers shifted up 32-bits so that any
userspace breakage will be detected really early on?