From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Jason Baron <jbaron@redhat.com>,
Jim Cromie <jim.cromie@gmail.com>, Kay Sievers <kay@vrfy.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] dynamic_debug: Restore dev_dbg functionality, optimize stack
Date: Thu, 02 Aug 2012 10:02:20 -0700 [thread overview]
Message-ID: <1343926940.2011.18.camel@joe2Laptop> (raw)
In-Reply-To: <20120731145534.5606e840.akpm@linux-foundation.org>
On Tue, 2012-07-31 at 14:55 -0700, Andrew Morton wrote:
> On Sat, 28 Jul 2012 00:55:07 -0700
> Joe Perches <joe@perches.com> wrote:
>
> > commit c4e00daaa9 ("driver-core: extend dev_printk() to pass structured data")
> > changed __dev_printk and broke dynamic-debug's ability to control the
> > dynamic prefix of dev_dbg(dev,..).
> >
> > dynamic_emit_prefix() adds "[tid] module:func:line:" to the output and
> > those additions got lost.
> >
> > In addition, the current dynamic debug code uses up to 3 recursion
> > levels via %pV. This can consume quite a bit of stack. Directly
> > call printk_emit to reduce the recursion depth.
[]
> > Changes in v2:
> >
> > o Fix dynamic_emit_prefix to always initialize output
> > o Call create_syslog_header and emit_printk from__netdev_printk and
> > eliminate call to dev_printk to remove another recursion via %pV
>
> This one causes an oops-on-boot
> (http://ozlabs.org/~akpm/stuff/IMG_20120731_144047.jpg). v1 didn't do
> that.
>
> config: http://ozlabs.org/~akpm/stuff/config-akpm2
>
Thanks. I'll fix it when I can.
Expect a week or so delay though.
I'm a bit busy on other projects and this one seems to
require additional testing.
cheers, Joe
prev parent reply other threads:[~2012-08-02 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1343334310.17538.32.camel@joe2Laptop>
2012-07-28 7:55 ` [PATCH v2] dynamic_debug: Restore dev_dbg functionality, optimize stack Joe Perches
2012-07-31 21:55 ` Andrew Morton
2012-08-02 17:02 ` Joe Perches [this message]
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=1343926940.2011.18.camel@joe2Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@redhat.com \
--cc=jim.cromie@gmail.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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