mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Henning P. Schmiedehausen" <hps@intermeta.de>,
	linux-kernel@vger.kernel.org
Cc: Andreas Dilger <adilger@clusterfs.com>
Subject: Re: [PATCH 2/3] Add extended attributes to ext2/3
Date: Wed, 16 Oct 2002 15:30:01 -0400	[thread overview]
Message-ID: <20021016193001.GB1335@think.thunk.org> (raw)
In-Reply-To: <20021016170539.GA1201@clusterfs.com>

On Wed, Oct 16, 2002 at 11:05:39AM -0600, Andreas Dilger wrote:
> Err, wouldn't that be a 2TB FILE limit, and not a FILESYSTEM limit?

Yes, sorry about that.

I just took a quick look at this, and the limit is unfortunately
fundamental to the VFS; the st_blocks in struct inode and struct kstat
is an unsigned long, which means that we're stuck with the 2TB limit
for *all* filesystems, even using the LFS API.  (Or rather, as you
point out, since no one apparently is doing any overflow checking, so
st_blocks will just be incorrect, even to callers using the stat64
call.)

A quick fix would be to make st_blocks in struct inode and struct
kstat take a __u64 instead of a unsigned long, but it will have a
performance impact.  What do folks think?

						- Ted

  reply	other threads:[~2002-10-16 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 22:20 tytso
2002-10-16  9:38 ` Henning P. Schmiedehausen
2002-10-16 16:16   ` Theodore Ts'o
2002-10-16 17:05     ` Andreas Dilger
2002-10-16 19:30       ` Theodore Ts'o [this message]
2002-10-19 18:36         ` Jan Kara
2002-10-16 17:50     ` Lorenzo Allegrucci
2002-10-16 18:32       ` Andreas Dilger
     [not found] ` <200210161336.27935.agruen@suse.de>
     [not found]   ` <3DAD8D5E.31E177BA@digeo.com>
2002-10-16 20:32     ` [PATCH] linux-2.5.43-mm1: Further xattr/acl cleanups Andreas Gruenbacher
2002-10-16 21:15       ` Andreas Gruenbacher

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=20021016193001.GB1335@think.thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@clusterfs.com \
    --cc=hps@intermeta.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®