All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Owen Hofmann <osh@google.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] cpu: Defer smpboot kthread unparking until CPU known to scheduler
Date: Wed, 30 Mar 2016 12:04:02 +0100	[thread overview]
Message-ID: <20160330110402.GA4783@ares> (raw)
In-Reply-To: <CANqFzA6frwwMPM6twMmhGWxDT7FeesKYmtceq4E6OScJNSeGEQ@mail.gmail.com>

On Wed, Mar 16, 2016 at 05:38:05PM -0700, Owen Hofmann wrote:
> Hi, this is a request to please include upstream commit
> 00df35f991914db6b8bde8cf09808e19a9cffc3d ("cpu: Defer smpboot kthread
> unparking until CPU known to scheduler") in stable trees >= 3.15 and <
> 4.1.
> 
> Upstream dd9d3843755da95f63dd3a376f62b3e45c011210 ("sched: Fix
> cpu_active_mask/cpu_online_mask race") was included in stable to fix a
> race condition that led to kthreads running on the wrong cpu and
> causing errors like "kernel BUG at kernel/smpboot.c:135!". This is
> especially likely when running as a virtualized guest.
> 
> However, the fix depends on the ordering introduced in the requested
> patch, so the issue remains in kernels between 3.15 when the bug was
> introduced, and 4.1 which has 00df35f9.
> --
> 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 Owen, I'll queue this for the 3.16 kernel.

Cheers,
--
Lu�s

      reply	other threads:[~2016-03-30 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17  0:38 [PATCH] cpu: Defer smpboot kthread unparking until CPU known to scheduler Owen Hofmann
2016-03-30 11:04 ` Luis Henriques [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=20160330110402.GA4783@ares \
    --to=luis.henriques@canonical.com \
    --cc=osh@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.