From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext4: use module parameters instead of debugfs for mballoc_debug
Date: Mon, 11 Feb 2013 10:04:20 -0600 [thread overview]
Message-ID: <51191684.5080201@redhat.com> (raw)
In-Reply-To: <20130211155428.GA6001@thunk.org>
On 2/11/13 9:54 AM, Theodore Ts'o wrote:
> On Mon, Feb 11, 2013 at 09:48:01AM -0600, Eric Sandeen wrote:
>>
>> As another thought, did you consider using dynamic debug for this, or is that
>> too much trickiness? Might be nice since usually a bug reporter won't have
>> a kernel built with CONFIG_EXT4_DEBUG . . .
>
> I had assumed that the long term direction was to use tracepoints,
> which also has the advantage of not requiring kernels built with
> CONFIG_EXT4_DEBUG.
I guess dynanmic debug wouldn't either, but yeah, tracepoints make
more sense I suppose.
> Hmm.... one thing though is if we want bug reporters to use
> tracepoints (as opposed to just developers), we'll need to have some
> pre-made shell scripts to make it easy for non-developers to enable
> tracepoints for various problems.
Yep the interface has always been a little clunky. :)
Thanks,
-Eric
> - Ted
>
next prev parent reply other threads:[~2013-02-11 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 1:42 [PATCH 1/2] ext4: use module parameters instead of debugfs for mballoc_debug Theodore Ts'o
2013-02-10 1:42 ` [PATCH 2/2] jbd2: use module parameters instead of debugfs for jbd_debug Theodore Ts'o
2013-02-11 15:36 ` [PATCH 1/2] ext4: use module parameters instead of debugfs for mballoc_debug Eric Sandeen
2013-02-11 15:48 ` Eric Sandeen
2013-02-11 15:54 ` Theodore Ts'o
2013-02-11 16:04 ` Eric Sandeen [this message]
2013-02-11 23:14 ` Dave Chinner
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=51191684.5080201@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.