mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Hillf Danton <dhillf@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Stable <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] stop_machine: dequeue work before signal completion
Date: Tue, 12 Feb 2013 09:38:12 -0800	[thread overview]
Message-ID: <20130212173812.GG7348@htj.dyndns.org> (raw)
In-Reply-To: <CAJd=RBAJdTewGVs2CFoto6ybnxUOJKHSF57nZQT25uF7B-b+fg@mail.gmail.com>

On Sun, Feb 10, 2013 at 01:26:11PM +0800, Hillf Danton wrote:
> When a CPU is finally put down in either CPU_UP_CANCELLED or
> CPU_POST_DEAD, cpu_stop_cpu_callback() signals immediate completion on
> all cpu_stop_works still queued on the dead CPU; unfortunately, this
> code is buggy in that it doesn't remove the canceled work items off
> the stopper->works leaving it corrupted, which will trigger BUG_ON()
> during CPU_UP_PREPARE if the CPU is brought back online.
> 
> This bug isn't easily triggered because CPU_DOWN has to race against
> cpu_stop calls and most, if not all, cpu stop users pin target CPUs.
> 
> Fix it by popping each work item off stopper->works.
> 
> Thanks Tejun for sharing commit message, again.
> 
> Signed-off-by: Hillf Danton <dhillf@gmail.com>
> Reviewed-by: Namhyung Kim <namhyung@kernel.org>
> Cc: stable@vger.kernel.org

Acked-by: Tejun Heo <tj@kernel.org>

Andrew, this one too.

Thank you!

-- 
tejun

  reply	other threads:[~2013-02-12 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  5:26 Hillf Danton
2013-02-12 17:38 ` Tejun Heo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-08  3:42 Hillf Danton
2013-02-08  8:22 ` Namhyung Kim
2013-02-08 12:03   ` Hillf Danton
2013-02-09 19:17 ` Tejun Heo

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=20130212173812.GG7348@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhillf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung@kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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®