From: Chris Wedgwood <cw@f00f.org>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
aviro@redhat.com, akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: 64-bit inode number issues
Date: Mon, 16 Oct 2006 23:02:54 -0700 [thread overview]
Message-ID: <20061017060254.GA30598@tuatara.stupidest.org> (raw)
In-Reply-To: <20061012183232.GG4141@kvack.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?
next prev parent reply other threads:[~2006-10-17 6:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 16:45 fscache review comments, part 1 Christoph Hellwig
2006-09-28 17:30 ` Andreas Dilger
2006-09-29 0:02 ` Christoph Hellwig
2006-09-29 1:51 ` Timothy Shimmin
2006-09-29 8:38 ` David Howells
2006-10-02 13:40 ` David Howells
2006-10-02 17:39 ` Andrew Morton
2006-10-02 21:41 ` Christoph Hellwig
2006-10-04 13:44 ` Al Viro
2006-10-04 14:18 ` 64-bit inode number issues David Howells
2006-10-07 21:01 ` Christoph Hellwig
2006-10-09 9:01 ` David Chinner
2006-10-09 11:32 ` David Howells
2006-10-09 14:12 ` Arjan van de Ven
2006-10-09 23:53 ` David Chinner
2006-10-12 18:32 ` Benjamin LaHaise
2006-10-17 6:02 ` Chris Wedgwood [this message]
2006-10-09 7:58 ` David Howells
2006-10-04 14:23 ` David Howells
2006-10-08 2:00 ` Theodore Tso
2006-10-08 16:02 ` Alexander Viro
2006-10-09 13:46 ` fscache review comments, part 1 David Howells
2006-10-10 13:31 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061017060254.GA30598@tuatara.stupidest.org \
--to=cw@f00f.org \
--cc=akpm@osdl.org \
--cc=aviro@redhat.com \
--cc=bcrl@kvack.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).