From: Eric Sandeen <sandeen@sandeen.net>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
yu kuai <yukuai3@huawei.com>
Cc: sandeen@redhat.com, billodo@redhat.com,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, zhengbin13@huawei.com
Subject: Re: [PATCH] xfs: include QUOTA, FATAL ASSERT build options in XFS_BUILD_OPTIONS
Date: Mon, 16 Sep 2019 12:16:53 -0500 [thread overview]
Message-ID: <d7b54271-9582-cdf7-7e61-9cb9aa239e6a@sandeen.net> (raw)
In-Reply-To: <20190916162406.GY2229799@magnolia>
On 9/16/19 11:24 AM, Darrick J. Wong wrote:
> On Fri, Sep 06, 2019 at 02:26:46PM +0800, yu kuai wrote:
>> In commit d03a2f1b9fa8 ("xfs: include WARN, REPAIR build options in
>> XFS_BUILD_OPTIONS"), Eric pointed out that the XFS_BUILD_OPTIONS string,
>> shown at module init time and in modinfo output, does not currently
>> include all available build options. So, he added in CONFIG_XFS_WARN and
>> CONFIG_XFS_REPAIR. However, this is not enough, add in CONFIG_XFS_QUOTA
>> and CONFIG_XFS_ASSERT_FATAL.
>>
>> Signed-off-by: yu kuai <yukuai3@huawei.com>
>> ---
>> fs/xfs/xfs_super.h | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/fs/xfs/xfs_super.h b/fs/xfs/xfs_super.h
>> index 763e43d..b552cf6 100644
>> --- a/fs/xfs/xfs_super.h
>> +++ b/fs/xfs/xfs_super.h
>> @@ -11,9 +11,11 @@
>> #ifdef CONFIG_XFS_QUOTA
>> extern int xfs_qm_init(void);
>> extern void xfs_qm_exit(void);
>> +# define XFS_QUOTA_STRING "quota, "
>> #else
>> # define xfs_qm_init() (0)
>> # define xfs_qm_exit() do { } while (0)
>> +# define XFS_QUOTA_STRING
>> #endif
>>
>> #ifdef CONFIG_XFS_POSIX_ACL
>> @@ -50,6 +52,12 @@ extern void xfs_qm_exit(void);
>> # define XFS_WARN_STRING
>> #endif
>>
>> +#ifdef CONFIG_XFS_ASSERT_FATAL
>> +# define XFS_ASSERT_FATAL_STRING "fatal assert, "
>
> /me wonders if the space here will screw up any scripts that try to
> parse the logging string, but OTOH that seems pretty questionable to me.
>
> Also, whatever happened to adding a sysfs file so that scripts (ok let's
> be honest, xfstests) could programmatically figure out the capabilities
> of the running xfs module?
I sent it ([PATCH] xfs: show build options in sysfs) but it was met with some
IMHO nonspecific commentary but never received a review, so was never merged.
-Eric
next prev parent reply other threads:[~2019-09-16 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 6:26 yu kuai
2019-09-16 16:24 ` Darrick J. Wong
2019-09-16 17:16 ` Eric Sandeen [this message]
2019-10-14 17:34 ` 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=d7b54271-9582-cdf7-7e61-9cb9aa239e6a@sandeen.net \
--to=sandeen@sandeen.net \
--cc=billodo@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
--cc=zhengbin13@huawei.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
all inboxes | Powered by JetHome®