From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: make fatal assert failures conditional in debug mode
Date: Wed, 10 May 2017 20:44:50 +1000 [thread overview]
Message-ID: <20170510104450.GJ17542@dastard> (raw)
In-Reply-To: <fb356789-56ab-757c-7c5f-b90d9ffbb1ea@sandeen.net>
On Mon, May 08, 2017 at 10:02:16PM -0500, Eric Sandeen wrote:
> On 5/8/17 6:14 PM, Dave Chinner wrote:
> >> So for me, the ability to live switch between BUG() or warn in debug
> >> mode doesn't add value. In fact, it is less ideal than just being able
> >> to (re)compile a kernel module and load it with expected behavior. That
>
> > Who uses kernel modules for testing?
>
> I do, all the time.
And I don't - haven't for years - but that misses the point of the
question. It was a rhetorical question attempting to make people
think about more than just their own workflow-specific details...
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-05-10 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 13:31 [PATCH v2] xfs: make fatal assert failures conditional in debug mode Brian Foster
2017-05-05 17:12 ` Bill O'Donnell
2017-05-05 23:09 ` Dave Chinner
2017-05-08 12:55 ` Brian Foster
2017-05-08 23:14 ` Dave Chinner
2017-05-09 3:02 ` Eric Sandeen
2017-05-10 10:44 ` Dave Chinner [this message]
2017-05-09 13:11 ` Brian Foster
2017-05-09 15:37 ` Darrick J. Wong
2017-05-09 17:00 ` Brian Foster
2017-05-09 17:20 ` Darrick J. Wong
2017-05-09 17:47 ` Brian Foster
2017-05-09 20:56 ` Darrick J. Wong
2017-05-10 10:54 ` Dave Chinner
2017-05-10 11:44 ` Brian Foster
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=20170510104450.GJ17542@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).