From: Tao Ma <tao.ma@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: viro@zeniv.linux.org.uk, drepper@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] add f_flags to struct statfs(64)
Date: Sun, 27 Jun 2010 15:55:24 +0800 [thread overview]
Message-ID: <4C2703EC.7050001@oracle.com> (raw)
In-Reply-To: <20100626093507.GB26371@lst.de>
Hi Christoph,
On 06/26/2010 05:35 PM, Christoph Hellwig wrote:
> Add a flags field to help glibc implementing statvfs(3) efficiently.
>
> We copy the flag values from glibc, and add a new ST_VALID flag to
> denote that f_flags is implemented.
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
>
<snip>
> Index: linux-2.6/include/asm-generic/statfs.h
> ===================================================================
> --- linux-2.6.orig/include/asm-generic/statfs.h 2010-06-26 09:26:56.000000000 +0200
> +++ linux-2.6/include/asm-generic/statfs.h 2010-06-26 10:00:33.868047809 +0200
> @@ -33,7 +33,8 @@ struct statfs {
> __kernel_fsid_t f_fsid;
> __statfs_word f_namelen;
> __statfs_word f_frsize;
> - __statfs_word f_spare[5];
> + __statfs_word f_flags;
> + __statfs_word f_spare[4];
> };
>
> /*
> @@ -55,7 +56,8 @@ struct statfs64 {
> __kernel_fsid_t f_fsid;
> __statfs_word f_namelen;
> __statfs_word f_frsize;
> - __statfs_word f_spare[5];
> + __statfs_word f_flags;
> + __statfs_word f_spare[4];
> } ARCH_PACK_STATFS64;
>
> /*
> @@ -77,6 +79,7 @@ struct compat_statfs64 {
> __kernel_fsid_t f_fsid;
> __u32 f_namelen;
> __u32 f_frsize;
> + __u32 f_flags[5];
> __u32 f_spare[5];
> } ARCH_PACK_COMPAT_STATFS64;
This is a typo?
Regards,
Tao
next prev parent reply other threads:[~2010-06-27 7:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 9:35 [PATCH 2/2] add f_flags to struct statfs(64) Christoph Hellwig
2010-06-26 9:56 ` Nick Piggin
2010-06-26 13:09 ` Christoph Hellwig
2010-06-26 13:16 ` Nick Piggin
2010-06-26 12:55 ` Neil Brown
2010-06-26 13:12 ` Christoph Hellwig
2010-06-27 7:55 ` Tao Ma [this message]
2010-06-27 9:20 ` Christoph Hellwig
2010-06-28 18:43 ` Andreas Dilger
2010-06-28 19:52 ` Ulrich Drepper
2010-06-28 20:07 ` Andreas Dilger
2010-06-29 8:57 ` Nick Piggin
2010-06-29 9:25 ` Christoph Hellwig
2010-06-29 9:59 ` Ulrich Drepper
2010-06-29 11:05 ` Nick Piggin
2010-06-29 12:57 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2010-07-07 16:53 Christoph Hellwig
2010-07-07 17:11 ` Ulrich Drepper
2010-07-07 17:31 ` Linus Torvalds
2010-07-07 17:33 ` Christoph Hellwig
2010-07-07 17:55 ` Miklos Szeredi
2010-07-07 18:06 ` Linus Torvalds
2010-07-07 18:50 ` Nick Piggin
2010-07-07 19:30 ` Linus Torvalds
2010-07-18 6:41 ` Christoph Hellwig
2010-07-18 17:03 ` Linus Torvalds
2010-07-07 18:16 ` Nick Piggin
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=4C2703EC.7050001@oracle.com \
--to=tao.ma@oracle.com \
--cc=drepper@redhat.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.