public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: tony.luck@intel.com, bp@amd64.org, tglx@linutronix.de,
	mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	Miao Xie <miaox@cn.fujitsu.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH] Do not change worker's running cpu in cmci_rediscover().
Date: Thu, 18 Oct 2012 11:42:39 +0800	[thread overview]
Message-ID: <507F7AAF.3070400@cn.fujitsu.com> (raw)
In-Reply-To: <20121016230824.GG16166@google.com>

On 10/17/2012 07:08 AM, Tejun Heo wrote:
> On Thu, Sep 27, 2012 at 05:19:46PM +0800, Tang Chen wrote:
>> 1. cmci_rediscover() is only called by the CPU_POST_DEAD event handler, which
>> means the corresponding cpu has already dead. As a result, it won't be accessed
>> in the for_each_online_cpu loop.
>> So, we could change the if(cpu == dying) statement into a BUG_ON().
>
> Let's please move this to a separate patch and use WARN_ON_ONCE()
> instead.

OK, no problem. :)

>
>> 2. cmci_rediscover() used set_cpus_allowed_ptr() to change the current process's
>> running cpu, and migrate itself to the dest cpu. But worker processes are not
>> allowed to be migrated. If current is a worker, the worker will be migrated to
>> another cpu, but the corresponding  worker_pool is still on the original cpu.
>>
>> In this case, the following BUG_ON in try_to_wake_up_local() will be triggered:
>> BUG_ON(rq != this_rq());
>>
>> This will cause the kernel panic.
>>
>> This patch removes the set_cpus_allowed_ptr() call, and put the cmci rediscover
>> jobs onto all the other cpus using system_wq. This could bring some delay for
>> the jobs.

> After separating out the fix part into a separate patch, please add
> Cc: stable@vger.kernel.org.

OK, I will.

>
> The change looks correct to me but fails to apply to the current
> mainline.

I'll update it and resend it soon. :)
Thanks.

>
> Thanks!
>


      reply	other threads:[~2012-10-18  3:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27  9:19 [PATCH] Do not change worker's running cpu in cmci_rediscover() Tang Chen
2012-09-28  7:54 ` Lai Jiangshan
2012-10-08  5:45   ` Tang Chen
2012-10-16 23:08 ` Tejun Heo
2012-10-18  3:42   ` Tang Chen [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=507F7AAF.3070400@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaox@cn.fujitsu.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@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