From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH RFC] xfs: support debug mode with assert warnings
Date: Thu, 4 May 2017 04:57:25 -0700 [thread overview]
Message-ID: <20170504115725.GB22052@infradead.org> (raw)
In-Reply-To: <20170502121423.GB6975@bfoster.bfoster>
On Tue, May 02, 2017 at 08:14:25AM -0400, Brian Foster wrote:
> As noted above, this is just a reuse of the flag. XFS_WARN and XFS_DEBUG
> are currently mutually exclusive. The former enables warnings on assert
> failures. The latter enables BUG()'s on assert failures and the
> additional, typical debug mode code. The Kconfig hack above simply pops
> up a conditional option when debug mode is enabled that effectively
> allows setting both XFS_WARN and XFS_DEBUG at the same time. The header
> files interpret this as debug mode enabled with an override for the
> assert failures to warn rather than BUG().
Oh, I didn't know Kconfig allows the same symbol to be define twice.
But even if that's ok I'd say it's rather odd.
> Note that this is just a hack and we can organize the Kconfig options
> however we want. For example, we could call this XFS_DEBUG_WARN and
> continue to consider it a debug mode sub-flag, or we could turn the
> debug mode option into a multi-mode selector (i.e., Debug modes: "None,"
> "Warn only," "Debug mode," "Debug mode w/ non-fatal asserts"). I played
> around a bit with the latter but it seems like a bit of overkill to me.
Maybe we need something like:
XFS_WARN (as-is)
XFS_WARN_BUG (XFS_WARN + BUG_ON on assert)
XFS_DEBUG (everyhing under XFS_DEBUG currently that's not related to
ASSERT)
next prev parent reply other threads:[~2017-05-04 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 17:29 [PATCH RFC] xfs: support debug mode with assert warnings Brian Foster
2017-05-02 7:37 ` Christoph Hellwig
2017-05-02 12:14 ` Brian Foster
2017-05-04 11:57 ` Christoph Hellwig [this message]
2017-05-04 12:44 ` Brian Foster
2017-05-04 16:41 ` 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=20170504115725.GB22052@infradead.org \
--to=hch@infradead.org \
--cc=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).