From: Ben Hutchings <ben@decadent.org.uk>
To: "Andreas Bießmann" <andreas@biessmann.de>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kay Sievers <kay@vrfy.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] register_console: prevent adding the same console twice
Date: Fri, 22 Mar 2013 18:36:08 +0000 [thread overview]
Message-ID: <1363977368.3728.35.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <1363947052-15605-1-git-send-email-andreas@biessmann.de>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
On Fri, 2013-03-22 at 11:10 +0100, Andreas Bießmann wrote:
> This patch guards the console_drivers list to be corrupted. The
> for_each_console() macro insist on a strictly forward list ended by NULL:
>
> con0->next->con1->next->NULL
>
> Without this patch it may happen easily to destroy this list for example by
> adding 'earlyprintk' twice. This will result in the following list:
>
> con0->next->con0
>
> This in turn will result in an endless loop in console_unlock() later on by
> printing the first __log_buf line endlessly.
>
> Signed-off-by: Andreas Bießmann <andreas@biessmann.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Kay Sievers <kay@vrfy.org>
> Cc: stable@vger.kernel.org
> ---
> kernel/printk.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/kernel/printk.c b/kernel/printk.c
> index 0b31715..f78bfcd 100644
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -2254,6 +2254,14 @@ void register_console(struct console *newcon)
> unsigned long flags;
> struct console *bcon = NULL;
>
> + if (console_drivers)
> + for_each_console(bcon)
> + if (bcon == newcon) {
> + pr_warn("prevent adding console '%s%d' twice\n",
> + newcon->name, newcon->index);
Since this is surely a bug in the calling driver, I think the warning
should be louder, i.e. use WARN.
Ben.
> + return;
> + }
> +
> /*
> * before we register a new CON_BOOT console, make sure we don't
> * already have a valid console
--
Ben Hutchings
Make three consecutive correct guesses and you will be considered an expert.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-03-22 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 10:10 Andreas Bießmann
2013-03-22 18:36 ` Ben Hutchings [this message]
2013-03-25 8:59 ` [PATCH v2] " Andreas Bießmann
2013-05-07 7:18 ` Andreas Bießmann
2013-08-02 10:23 ` [RESEND][PATCH " Andreas Bießmann
2013-08-02 10:37 ` Greg Kroah-Hartman
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=1363977368.3728.35.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=andreas@biessmann.de \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®