diff options
| author |   Jason Baron <jbaron@redhat.com> | 2008-10-27 12:05:14 -0400 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@suse.de> | 2008-10-29 15:03:50 -0700 |
| commit | 113328306dbdfd5f146f257e447364dc66d025d4 (patch) | |
| tree | a62ad2388617b8e7943ed9133a582a3fcef7f0da /fs/jbd2/commit.c | |
| parent | HOWTO: Sync patch for jp_JP/HOWTO (diff) | |
| download | linux-dev-113328306dbdfd5f146f257e447364dc66d025d4.tar.xz linux-dev-113328306dbdfd5f146f257e447364dc66d025d4.zip | |
Driver core: fix 'dynamic_debug' cmd line parameter
In testing 2.6.28-rc1, I found that passing 'dynamic_printk' on the command
line didn't activate the debug code. The problem is that dynamic_printk_setup()
(which activates the debugging) is being called before dynamic_printk_init() is
called (which initializes infrastructure). Fix this by setting setting the
state to 'DYNAMIC_ENABLED_ALL' in dynamic_printk_setup(), which will also
cause all subsequent modules to have debugging automatically started, which is
probably the behavior we want.
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions