From: Andrew Morton <akpm@osdl.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: VFS: Convert abuses of sector_t
Date: Wed, 22 Mar 2006 02:50:25 -0800 [thread overview]
Message-ID: <20060322025025.662999e9.akpm@osdl.org> (raw)
In-Reply-To: <1142961196.7987.17.camel@lade.trondhjem.org>
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> From: Trond Myklebust <Trond.Myklebust@netapp.com>
>
> The type "sector_t" is heavily tied in to the block layer interface as an
> offset/handle to a block, and is subject to a supposedly block-specific
> configuration option: CONFIG_LBD. Despite this, it is used in struct
> kstatfs to save a couple of bytes on the stack whenever we call the
> filesystems' ->statfs().
>
> One consequence is that networked filesystems may break if CONFIG_LBD is
> not set, since it is quite common to have multi-TB remote filesystems.
>
> The following patch just converts struct kstatfs to use the standard type u64.
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
> ---
>
> include/linux/statfs.h | 10 +++++-----
> 1 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/statfs.h b/include/linux/statfs.h
> index ad83a2b..b34cc82 100644
> --- a/include/linux/statfs.h
> +++ b/include/linux/statfs.h
> @@ -8,11 +8,11 @@
> struct kstatfs {
> long f_type;
> long f_bsize;
> - sector_t f_blocks;
> - sector_t f_bfree;
> - sector_t f_bavail;
> - sector_t f_files;
> - sector_t f_ffree;
> + u64 f_blocks;
> + u64 f_bfree;
> + u64 f_bavail;
> + u64 f_files;
> + u64 f_ffree;
> __kernel_fsid_t f_fsid;
> long f_namelen;
> long f_frsize;
This change also appears (for different reasons) in
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc6/2.6.16-rc6-mm2/broken-out/2tb-files-change-type-of-kstatfs-entries.patch,
so we should be OK.
prev parent reply other threads:[~2006-03-22 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:13 Trond Myklebust
2006-03-22 10:50 ` Andrew Morton [this message]
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=20060322025025.662999e9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®