public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Andreas Bießmann" <andreas@biessmann.de>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay@vrfy.org>,
	Ben Hutchings <ben@decadent.org.uk>,
	stable@vger.kernel.org
Subject: Re: [RESEND][PATCH v2] register_console: prevent adding the same console twice
Date: Fri, 2 Aug 2013 18:37:44 +0800	[thread overview]
Message-ID: <20130802103744.GA6356@kroah.com> (raw)
In-Reply-To: <1375439014-13679-1-git-send-email-andreas@biessmann.de>

On Fri, Aug 02, 2013 at 12:23:34PM +0200, 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, especially on embedded devices where the early
> console is often a single static instance.  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: Ben Hutchings <ben@decadent.org.uk>
> Cc: stable@vger.kernel.org

It's a nice "feature", but I fail to see how this is worthy of going
into the stable tree, as it's not fixing a kernel error, only a typo by
a user.

thanks,

greg k-h

      reply	other threads:[~2013-08-02 10:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 10:10 [PATCH] register_console: prevent adding the same console twice Andreas Bießmann
2013-03-22 18:36 ` Ben Hutchings
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 [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=20130802103744.GA6356@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas@biessmann.de \
    --cc=ben@decadent.org.uk \
    --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