From: Bill O'Donnell <billodo@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] include WARN, REPAIR build options in XFS_BUILD_OPTIONS
Date: Wed, 5 Jun 2019 08:08:12 -0500 [thread overview]
Message-ID: <20190605130812.GA9823@redhat.com> (raw)
In-Reply-To: <15ed3957-d4f5-01a0-3d2e-d8a69cc435ce@redhat.com>
On Tue, Jun 04, 2019 at 06:23:25PM -0500, Eric Sandeen wrote:
> The XFS_BUILD_OPTIONS string, shown at module init time and
> in modinfo output, does not currently include all available
> build options. So, add in CONFIG_XFS_WARN and CONFIG_XFS_REPAIR.
>
> It has been suggested in some quarters
> That this is not enough.
> Well ...
I saw what you did there ;)
Reviewed-by: Bill O'Donnell <billodo@redhat.com>
>
> Anybody who would like to see this in a sysfs file can send
> a patch. :)
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> I might send that patch, but would like to have the string
> advertising build options be complete, for now.
>
> diff --git a/fs/xfs/xfs_super.h b/fs/xfs/xfs_super.h
> index 21cb49a..763e43d 100644
> --- a/fs/xfs/xfs_super.h
> +++ b/fs/xfs/xfs_super.h
> @@ -38,6 +38,18 @@
> # define XFS_SCRUB_STRING
> #endif
>
> +#ifdef CONFIG_XFS_ONLINE_REPAIR
> +# define XFS_REPAIR_STRING "repair, "
> +#else
> +# define XFS_REPAIR_STRING
> +#endif
> +
> +#ifdef CONFIG_XFS_WARN
> +# define XFS_WARN_STRING "verbose warnings, "
> +#else
> +# define XFS_WARN_STRING
> +#endif
> +
> #ifdef DEBUG
> # define XFS_DBG_STRING "debug"
> #else
> @@ -49,6 +61,8 @@
> XFS_SECURITY_STRING \
> XFS_REALTIME_STRING \
> XFS_SCRUB_STRING \
> + XFS_REPAIR_STRING \
> + XFS_WARN_STRING \
> XFS_DBG_STRING /* DBG must be last */
>
> struct xfs_inode;
>
next prev parent reply other threads:[~2019-06-05 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 23:23 [PATCH] include WARN, REPAIR build options in XFS_BUILD_OPTIONS Eric Sandeen
2019-06-05 13:08 ` Bill O'Donnell [this message]
2019-06-05 15:13 ` Darrick J. Wong
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=20190605130812.GA9823@redhat.com \
--to=billodo@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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