stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: stable@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: Re: printk: queue wake_up_klogd irq_work only if per-CPU areas are ready
Date: Mon, 20 Jul 2020 14:50:41 +0200	[thread overview]
Message-ID: <20200720125041.GC3147730@kroah.com> (raw)
In-Reply-To: <20200414131309.GE12779@google.com>

On Tue, Apr 14, 2020 at 10:13:09PM +0900, Sergey Senozhatsky wrote:
> On (20/04/14 14:14), Greg KH wrote:
> > On Tue, Apr 14, 2020 at 09:06:13PM +0900, Sergey Senozhatsky wrote:
> > > Hello,
> > > 
> > > Commit ab6f762f0f53162d41 Linus' HEAD.
> > > 
> > > printk_deferred() does not make sure that it's safe to write to
> > > per-CPU data, which causes problems when printk_deferred() is
> > > invoked "too early", before per-CPU areas are initialized. There
> > > are multiple bug reports, e.g.
> > > https://bugzilla.kernel.org/show_bug.cgi?id=206847
> > > 
> > > 	-ss
> > 
> > So where do you want this commit backported to?
> 
> Well,  printk() is affected in all the kernels where
> printk_deferred() relies on per-CPU data. Which may
> translate to "pretty much all current stable kernels?"
> This patch, however, uses printk_safe() bits, so it
> won't apply on pre-printk_safe() kernels (not sure if
> we have such -stable kernels though).

This is already in the 5.4.y tree, so I've added it to 4.19.y, but I
could not apply it to anything older (4.14.y, 4.9.y, 4.4.y) as it did
not apply there.

If you want it in those older kernels, and you think it is really
needed, please feel free to send a backported version for them.

thanks,

greg k-h

      reply	other threads:[~2020-07-20 12:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 12:06 printk: queue wake_up_klogd irq_work only if per-CPU areas are ready Sergey Senozhatsky
2020-04-14 12:14 ` Greg KH
2020-04-14 13:13   ` Sergey Senozhatsky
2020-07-20 12:50     ` Greg KH [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=20200720125041.GC3147730@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky.work@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).