summaryrefslogtreecommitdiff
path: root/fs/xfs/xfs_globals.c
diff options
context:
space:
mode:
authorBrian Foster <bfoster@redhat.com>2017-06-15 07:29:13 +0300
committerDarrick J. Wong <darrick.wong@oracle.com>2017-06-19 18:59:10 +0300
commit1040960efaabb8e6c87633c7becbb51fc99d4b9b (patch)
tree748f34ddc548e817ac3ec698d943c0ee10ac3444 /fs/xfs/xfs_globals.c
parentccdab3d6e881649f05110d9098fd248d2753aaf3 (diff)
downloadlinux-1040960efaabb8e6c87633c7becbb51fc99d4b9b.tar.xz
xfs: define fatal assert build time tunable
While configurable at runtime, the DEBUG mode assert failure behavior is usually either desired or not for a particular situation. For example, developers using kernel modules may prefer for fatal asserts to remain disabled across module reloads while QE engineers doing broad regression testing may prefer to have fatal asserts enabled on boot to facilitate data collection for bug reports. To provide a compromise/convenience for developers, create a Kconfig option that sets the default value of the DEBUG mode 'bug_on_assert' sysfs tunable. The default behavior remains to trigger kernel BUGs on assert failures to preserve existing behavior across kernel configuration updates with DEBUG mode enabled. Signed-off-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Diffstat (limited to 'fs/xfs/xfs_globals.c')
-rw-r--r--fs/xfs/xfs_globals.c7
1 files changed, 5 insertions, 2 deletions
diff --git a/fs/xfs/xfs_globals.c b/fs/xfs/xfs_globals.c
index 673adf0a40cc..3e1cc3001bcb 100644
--- a/fs/xfs/xfs_globals.c
+++ b/fs/xfs/xfs_globals.c
@@ -47,6 +47,9 @@ xfs_param_t xfs_params = {
struct xfs_globals xfs_globals = {
.log_recovery_delay = 0, /* no delay by default */
- .bug_on_assert = true, /* historical default in DEBUG
- * mode */
+#ifdef XFS_ASSERT_FATAL
+ .bug_on_assert = true, /* assert failures BUG() */
+#else
+ .bug_on_assert = false, /* assert failures WARN() */
+#endif
};