From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v3 0/2] xfs: make fatal assert failures conditional in debug mode
Date: Wed, 10 May 2017 10:31:49 -0400 [thread overview]
Message-ID: <1494426711-6934-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
This version makes fatal asserts runtime and build time configurable.
Patch 1 creates the runtime tunable and patch 2 creates a Kconfig option
to control the default value of the runtime tunable. As before, default
DEBUG mode behavior is preserved (i.e., assert failures BUG() the
kernel).
Brian
v3:
- Add DEBUG mode sysfs tunable for runtime configuration.
- Refactor compile time flag to set default value of runtime flag.
v2: http://www.spinics.net/lists/linux-xfs/msg06520.html
- Clean up the Kconfig option help text.
v1: http://www.spinics.net/lists/linux-xfs/msg06498.html
- Use a new config option rather than reuse XFS_WARN.
- Disable BUG() in DEBUG mode by default and flip the logic of the new
config option.
rfc: http://www.spinics.net/lists/linux-xfs/msg06390.html
Brian Foster (2):
xfs: define bug_on_assert debug mode sysfs tunable
xfs: define fatal assert build time tunable
fs/xfs/Kconfig | 13 +++++++++++++
fs/xfs/xfs.h | 4 ++++
fs/xfs/xfs_globals.c | 5 +++++
fs/xfs/xfs_message.c | 5 ++++-
fs/xfs/xfs_sysctl.h | 1 +
fs/xfs/xfs_sysfs.c | 33 +++++++++++++++++++++++++++++++++
6 files changed, 60 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2017-05-10 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 14:31 Brian Foster [this message]
2017-05-10 14:31 ` [PATCH v3 1/2] xfs: define bug_on_assert debug mode sysfs tunable Brian Foster
2017-05-10 14:31 ` [PATCH v3 2/2] xfs: define fatal assert build time tunable Brian Foster
2017-05-31 15:36 ` 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=1494426711-6934-1-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).