From: Andrew Morton <akpm@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: fscache review comments, part 1
Date: Mon, 2 Oct 2006 10:39:00 -0700 [thread overview]
Message-ID: <20061002103900.5b239d9f.akpm@osdl.org> (raw)
In-Reply-To: <20489.1159796454@warthog.cambridge.redhat.com>
On Mon, 02 Oct 2006 14:40:54 +0100
David Howells <dhowells@redhat.com> wrote:
> Christoph Hellwig <hch@infradead.org> wrote:
>
> > Unfortunately there's a lot of broken userspace that can't deal
> > with 64bit inode numbers, so you need to make the lod behaviour
> > a mount option at least, probably even the default. Given that
> > we're going to run into problems like that it might make sense
> > to make the option VFS-level instead of just in nfs. (Note:
> > XFS already has an option like that)
>
> This really needs fixing quite urgently. We've seen it break ld.so/libdl (and
> other things, but dynamic loading is one of the major pains as it's not
> entirely obvious).
>
Speaking of which.. I've been having struggling a bit with
vfs-make-filldir_t-and-struct-kstat-deal-in-64-bit-inode-numbers.patch
nfs-represent-64-bit-fileids-as-64-bit-inode-numbers-on-32-bit-systems.patch
I don't have a good understanding of what the implications are for userspace.
What are the risks and what are the advantages and what the level of urgency
is behind those patches.
Help?
next prev parent reply other threads:[~2006-10-02 17:39 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 [this message]
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
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=20061002103900.5b239d9f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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).