public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: "kgdb-bugreport@lists.sourceforge.net" 
	<kgdb-bugreport@lists.sourceforge.net>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kdb:  Avoid using dbg_io_ops until it is initialized
Date: Tue, 20 Mar 2012 14:31:52 -0700	[thread overview]
Message-ID: <4F68F748.7010304@am.sony.com> (raw)
In-Reply-To: <4F68CF7E.8070605@windriver.com>

On 03/20/2012 11:42 AM, Jason Wessel wrote:
> On 09/21/2011 03:19 PM, Tim Bird wrote:
>> This fixes a bug with setting a breakpoint during kdb initialization
>> (from kdb_cmds). Any call to kdb_printf() before the initialization
>> of the kgdboc serial console driver (which happens much later during
>> bootup than kdb_init), results in kernel panic due to the use of
>> dbg_io_ops before it is initialized.
> 
> I added this patch to the merge queue for the 3.4 kernel.
> 
> In the test and review of this patch, I thought there might be another
> race condition with kdb pager, but this is not the case.  The run time
> validation shows that the kdb pager can only get activated by entering
> and configuring the kdb shell and it is turned off on exit, so we are
> all set and no further changes are needed.

Thanks!
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================


      reply	other threads:[~2012-03-20 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 20:19 [PATCH] kdb: Avoid using dbg_io_ops until it is initialized Tim Bird
2011-09-22  2:52 ` [Kgdb-bugreport] " Dongdong Deng
2011-09-22 17:39   ` Tim Bird
2012-03-20 18:42 ` Jason Wessel
2012-03-20 21:31   ` Tim Bird [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=4F68F748.7010304@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@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