From: Milton Miller <miltonm@bga.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Mackerras <paulus@samba.org>,
ppc64-dev <linuxppc64-dev@ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
Greg Edwards <edwardsg@sgi.com>,
Anton Blanchard <anton@samba.org>, Linus <torvalds@osdl.org>
Subject: Re: [PATCH] ppc64: iSeries early printk breakage
Date: Wed, 7 Sep 2005 06:04:36 -0500 [thread overview]
Message-ID: <ccb92a396938e8c1d00b46d122d6583c@bga.com> (raw)
In-Reply-To: <20050907195238.5523dada.sfr@canb.auug.org.au>
Does anything actually break without this patch?
My reading of unregister_console says we will acquire
the console semaphore, walk the list, fail to find the
console, relase the semaphore, and return.
Hmm... unless there is a problem with the console preference
code? I don't see anything that should deref a bad pointer,
maybe it breaks the preference?
From get web:
if (console_drivers == NULL)
preferred_console = selected_console;
else if (console->flags & CON_CONSDEV)
console_drivers->flags |= CON_CONSDEV;
On Sep 7, 2005, at 4:52 AM, Stephen Rothwell wrote:
> The earlier commit 8d9273918635f0301368c01b56c03a6f339e8d51
> (Consolidate early console and PPCDBG code) broke iSeries because
> it caused unregister_console(&udbg_console) to be called
> unconditionally. iSeries never registers the udbg_console.
>
> This just reverts part of the change.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>
> arch/ppc64/kernel/udbg.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
> 234f5032f6ccb4d72e4b74d33af55716b67d8a27
> diff --git a/arch/ppc64/kernel/udbg.c b/arch/ppc64/kernel/udbg.c
> --- a/arch/ppc64/kernel/udbg.c
> +++ b/arch/ppc64/kernel/udbg.c
> @@ -158,14 +158,20 @@ static struct console udbg_console = {
> .index = -1,
> };
>
> +static int early_console_initialized;
> +
> void __init disable_early_printk(void)
> {
> + if (!early_console_initialized)
> + return;
> unregister_console(&udbg_console);
> + early_console_initialized = 0;
> }
>
> /* called by setup_system */
> void register_early_udbg_console(void)
> {
> + early_console_initialized = 1;
> register_console(&udbg_console);
> }
>
next prev parent reply other threads:[~2005-09-07 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 9:52 Stephen Rothwell
2005-09-07 11:04 ` Milton Miller [this message]
2005-09-08 1:01 ` Stephen Rothwell
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=ccb92a396938e8c1d00b46d122d6583c@bga.com \
--to=miltonm@bga.com \
--cc=anton@samba.org \
--cc=edwardsg@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®