mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: yur@emcraft.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] shmem: respect MAX_LFS_FILESIZE
Date: Fri, 10 Apr 2009 10:28:50 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0904101007200.2667@blonde.anvils> (raw)
In-Reply-To: <20090409163610.8619bfc7.akpm@linux-foundation.org>

On Thu, 9 Apr 2009, Andrew Morton wrote:
> On Mon, 6 Apr 2009 21:56:13 +0100 (BST)
> Hugh Dickins <hugh@veritas.com> wrote:
> 
> > Question: couldn't the 32-bit kernel's MAX_LFS_FILESIZE be almost doubled?
> > It limits the pagecache index to a signed long, but we use an unsigned long.
> 
> I expect it would be OK, yes.  The only failure mode I can think of is
> if someone is using signed long as a pagecache index and I'd be pretty
> surprised if we've made that mistake anywhere.  The potential for goofs
> is higher down in filesystems, but they shouldn't be using pagecache
> indices much at all.
> 
> Of course it does invite people to write applications which then fail
> on older kernels, but such is life.

Hmm, that's a very good point, and I doubt Ned Kelly can have the
last word on it.  Good filesystems go to a great deal of trouble over
the compatibility issues of new features: it would be rather sad to
blow that all away with a careless doubling of MAX_LFS_FILESIZE.

Or I'm talking nonsense: we already have this issue, when using
a 32-bit kernel to look at big files created with a 64-bit kernel.

But even so, I think I'll leave this change to someone braver.

Hugh

  reply	other threads:[~2009-04-10  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 20:54 [PATCH 1/3] shmem: fix division by zero Hugh Dickins
2009-04-06 20:56 ` [PATCH 2/3] shmem: respect MAX_LFS_FILESIZE Hugh Dickins
2009-04-09 23:36   ` Andrew Morton
2009-04-10  9:28     ` Hugh Dickins [this message]
2009-04-06 21:01 ` [PATCH 3/3] powerpc: allow 256kB pages with SHMEM Hugh Dickins
2009-04-07  3:28   ` Paul Mackerras
2009-04-07  6:10     ` Hugh Dickins
2009-04-09 23:34   ` Andrew Morton
2009-04-10  8:58     ` Hugh Dickins
2009-04-16 16:50   ` Ilya Yanok

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=Pine.LNX.4.64.0904101007200.2667@blonde.anvils \
    --to=hugh@veritas.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yur@emcraft.com \
    /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

all inboxes | Powered by JetHome®