From: Nathan Scott <nscott@aconex.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, RFC] put xfs build features into the stats file
Date: Mon, 20 Apr 2009 12:59:28 +1000 (EST) [thread overview]
Message-ID: <1520890652.3597921240196368192.JavaMail.root@mail-au.aconex.com> (raw)
In-Reply-To: <49EBDF30.90702@sandeen.net>
Separate file? That line uses a comma separator ... differs to
every other line in that stats file, painful for parsers. And
no risk of breaking anything if its a separate file.
cheers.
----- "Eric Sandeen" <sandeen@sandeen.net> wrote:
> Running xfstests on an xfs build w/o xattrs enabled, I realized
> there's no reliable way to see if the running xfs has various
> features other than debug (which is shown in /proc/fs/xfs/stat)
>
> What do folks think of adding the BUILD_OPTIONS to this file
> as well?
>
> # cat /proc/fs/xfs/stat
> extent_alloc 0 0 0 0
> ...
> xpc 0 0 0
> debug 0
> features security attributes, large block numbers, no debug
>
> Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
> ---
>
> Index: linux-2.6/fs/xfs/linux-2.6/xfs_stats.c
> ===================================================================
> --- linux-2.6.orig/fs/xfs/linux-2.6/xfs_stats.c
> +++ linux-2.6/fs/xfs/linux-2.6/xfs_stats.c
> @@ -89,6 +89,8 @@ xfs_read_xfsstats(
> 0);
> #endif
>
> + len += sprintf(buffer + len, "features " XFS_BUILD_OPTIONS "\n");
> +
> if (offset >= len) {
> *start = buffer;
> *eof = 1;
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
--
Nathan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-20 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 2:34 [PATCH, RFC] put xfs build features into the stats file Eric Sandeen
2009-04-20 2:59 ` Nathan Scott [this message]
2009-04-20 3:00 ` Eric Sandeen
2009-04-21 14:15 ` Christoph Hellwig
2009-04-21 15:20 ` Eric Sandeen
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=1520890652.3597921240196368192.JavaMail.root@mail-au.aconex.com \
--to=nscott@aconex.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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 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.