stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Preeti U Murthy <preeti@linux.vnet.ibm.com>,
	stable kernel team <stable@vger.kernel.org>,
	peterz@infradead.org, paulmck@linux.vnet.ibm.com, hpa@zytor.com,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/urgent] timers/tick/broadcast-hrtimer:  Fix suspicious RCU usage in idle loop
Date: Mon, 30 Mar 2015 11:26:16 +0100	[thread overview]
Message-ID: <20150330102616.GD20509@charon.olymp> (raw)
In-Reply-To: <20150329070447.GC18007@gmail.com>

On Sun, Mar 29, 2015 at 09:04:47AM +0200, Ingo Molnar wrote:
> 
> * Preeti U Murthy <preeti@linux.vnet.ibm.com> wrote:
> 
> > Hi,
> > 
> > Can you please add stable@vger.kernel.org to the Cc?
> > Without the patch, we get RCU warnings during bootup.
> > Hence the patch is important for the stable kernels as well.
> 
> This fix is now upstream.
> 
> Greg, please back-port the following upstream commit to -stable:
> 
>   a127d2bcf1fb ("timers/tick/broadcast-hrtimer: Fix suspicious RCU usage in idle loop")
> 
> this bug was introduced in v3.15 and will cleanly apply to v3.15 and 
> all later stable kernels.
> 
> Thanks,
> 
> 	Ingo
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Thanks, I'm queuing this for the 3.16 kernel as well.

Cheers,
--
Lu�s

  reply	other threads:[~2015-03-30 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150318104705.17763.56668.stgit@preeti.in.ibm.com>
     [not found] ` <tip-a127d2bcf1fbc8c8e0b5cf0dab54f7d3ff50ce47@git.kernel.org>
     [not found]   ` <55138184.3000801@linux.vnet.ibm.com>
2015-03-29  7:04     ` [tip:timers/urgent] timers/tick/broadcast-hrtimer: Fix suspicious RCU usage in idle loop Ingo Molnar
2015-03-30 10:26       ` Luis Henriques [this message]
2015-04-17 13:12       ` Greg KH

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=20150330102616.GD20509@charon.olymp \
    --to=luis.henriques@canonical.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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).