linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <jjherne@linux.vnet.ibm.com>,
	Sasha Levin <sasha.levin@oracle.com>, Tejun Heo <tj@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: workqueue: WARN at at kernel/workqueue.c:2176
Date: Wed, 4 Jun 2014 10:27:25 +0800	[thread overview]
Message-ID: <538E840D.2040300@cn.fujitsu.com> (raw)
In-Reply-To: <20140603141659.GO30445@twins.programming.kicks-ass.net>

On 06/03/2014 10:16 PM, Peter Zijlstra wrote:
> On Tue, Jun 03, 2014 at 07:24:38PM +0800, Lai Jiangshan wrote:
>> Hi, Jason
>>
>> Could you test again after the following command has done.
>> (if Peter hasn't asked you test with this command before nor he doesn't stop you now) 
>>
>> echo NO_TTWU_QUEUE > /sys/kernel/debug/sched_features
>>
>> Thanks a lot.
>>
>> Hi, Peter,
>>
>> I found something strange by review (just by review, no test yet)
>>
>> __migrate_task()
>> {
>> ...
>> 	/*
>> 	 * If we're not on a rq, the next wake-up will ensure we're
>> 	 * placed properly.
>> 	 */
>> 	if (p->on_rq) {
>> 		dequeue_task(rq_src, p, 0);
>> 		set_task_cpu(p, dest_cpu);
>> 		enqueue_task(rq_dest, p, 0);
>> 		check_preempt_curr(rq_dest, p, 0);
>> 	}
>> ...
>> }
>>
>> The comment is incorrect if TTWU_QUEUE is enabled.
>> The task is waken-up even p->on_rq==0 in this case:
>> 	p->wake_entry is added to the rq,
>> 	p->state is TASK_WAKING
>> 	p->on_rq is 0
>>
>> In this case __migrate_task() fails to migrate the task!!!.
>>
>> Go back to workqueue for higher level analysing.
>>
>> task1				cpu#4			task3
>> workqueue_cpu_up_callback()
>> 							wake_up_process(worker1)
>> 							  ttwu_queue_remote() #queue worker1 to cpu#4
>> set_cpus_allowed_ptr()
>>   set worker's cpuallowed to
>>   cpumask_of(5)
>> 				#stopper_task
>> 				__migrate_task()
>> 				finds p->on_rq is 0,
>> 				do nothing return
>> set_cpus_allowed_ptr() return 0
>>
>> In this case, the WARN_ON() in process_one_work() hit.
> 
> Hmm, yes I think you're right. A queued wakeup can miss an affinity
> change like that.
> 
> Something like the below ought to cure that I suppose..

As a non-scheduler developer, I can't find anything wrong with the patch
(I searched all on_rq in kernel/sched).

but I think __migrate_task() is slow path comparing to sched_ttwu_pending().
So I prefer to change set_cpus_allowed_ptr() and __migrate_task() rather than
to sched_ttwu_pending().

Any way, I agree on the change.
I hope Jason test it in few days.

> 
> ---
>  kernel/sched/core.c | 21 +++++++++++++++------
>  1 file changed, 15 insertions(+), 6 deletions(-)
> 
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 240aa83e73f5..0708ee21632f 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1521,17 +1521,32 @@ static int ttwu_remote(struct task_struct *p, int wake_flags)
>  }
>  
>  #ifdef CONFIG_SMP
> +static void ttwu_queue_remote(struct task_struct *p, int cpu)
> +{
> +	if (llist_add(&p->wake_entry, &cpu_rq(cpu)->wake_list))
> +		smp_send_reschedule(cpu);
> +}
> +
>  static void sched_ttwu_pending(void)
>  {
>  	struct rq *rq = this_rq();
>  	struct llist_node *llist = llist_del_all(&rq->wake_list);
>  	struct task_struct *p;
> +	int cpu;
>  
>  	raw_spin_lock(&rq->lock);
>  
>  	while (llist) {
>  		p = llist_entry(llist, struct task_struct, wake_entry);
>  		llist = llist_next(llist);
> +
> +		if (unlikely(!cpumask_test_cpu(rq->cpu, tsk_cpus_allowed(p)))) {
> +			cpu = select_fallback_rq(rq->cpu, p);
> +			set_task_cpu(p, cpu);
> +			ttwu_queue_remote(p, cpu);
> +			continue;
> +		}
> +
>  		ttwu_do_activate(rq, p, 0);
>  	}
>  
> @@ -1579,12 +1594,6 @@ void scheduler_ipi(void)
>  	irq_exit();
>  }
>  
> -static void ttwu_queue_remote(struct task_struct *p, int cpu)
> -{
> -	if (llist_add(&p->wake_entry, &cpu_rq(cpu)->wake_list))
> -		smp_send_reschedule(cpu);
> -}
> -
>  bool cpus_share_cache(int this_cpu, int that_cpu)
>  {
>  	return per_cpu(sd_llc_id, this_cpu) == per_cpu(sd_llc_id, that_cpu);


  reply	other threads:[~2014-06-04  2:23 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 18:58 workqueue: WARN at at kernel/workqueue.c:2176 Sasha Levin
2014-05-12 20:01 ` Tejun Heo
2014-05-13  2:19   ` Lai Jiangshan
2014-05-13  2:17     ` Sasha Levin
2014-05-14 16:52       ` Jason J. Herne
2014-05-16  3:50         ` Lai Jiangshan
2014-05-16  9:35           ` Peter Zijlstra
2014-05-16  9:56             ` Lai Jiangshan
2014-05-16 10:29               ` Peter Zijlstra
2014-05-16 10:15             ` Peter Zijlstra
2014-05-16 10:16               ` Peter Zijlstra
2014-05-16 10:39                 ` Peter Zijlstra
2014-05-16 11:57           ` Peter Zijlstra
2014-05-16 12:08             ` Tejun Heo
2014-05-16 12:14               ` Thomas Gleixner
2014-05-16 12:16                 ` Tejun Heo
2014-05-16 16:18             ` Lai Jiangshan
2014-05-16 16:29               ` Peter Zijlstra
2014-05-27 14:18                 ` Jason J. Herne
2014-05-27 14:26                   ` Peter Zijlstra
2014-05-29 16:23                     ` Jason J. Herne
2014-06-03 11:24                       ` Lai Jiangshan
2014-06-03 12:45                         ` Lai Jiangshan
2014-06-03 14:28                           ` Peter Zijlstra
2014-06-04  1:47                             ` Lai Jiangshan
2014-06-03 14:16                         ` Peter Zijlstra
2014-06-04  2:27                           ` Lai Jiangshan [this message]
2014-06-04  6:49                             ` Peter Zijlstra
2014-06-04  8:25                               ` Lai Jiangshan
2014-06-04  9:39                                 ` Peter Zijlstra
2014-06-05 10:54                                   ` Lai Jiangshan
2014-06-05 15:22                                     ` Jason J. Herne
2014-06-06 12:39                                     ` Jason J. Herne
2014-06-06 13:36                                     ` Peter Zijlstra
2014-06-08  2:50                                       ` Lai Jiangshan
2014-09-01  3:04                                       ` Lai Jiangshan
2014-09-03 15:15                                         ` Peter Zijlstra
2014-09-04  2:22                                           ` Lai Jiangshan
2014-09-04  6:39                                             ` Peter Zijlstra
2014-06-09 14:01                                     ` Jason J. Herne
2014-06-10  1:21                                       ` Lai Jiangshan
2014-06-16  1:30                                         ` Lai Jiangshan
2014-09-09 14:52                                 ` [tip:sched/core] sched: Migrate waking tasks tip-bot for Lai Jiangshan
2014-09-10  7:38                                   ` Kirill Tkhai
2014-09-10  7:53                                     ` Peter Zijlstra
2014-06-04  2:28                         ` workqueue: WARN at at kernel/workqueue.c:2176 Lai Jiangshan
2014-06-04  6:48                           ` Peter Zijlstra
2014-05-19 13:07           ` [tip:sched/core] sched: Fix hotplug vs set_cpus_allowed_ptr() tip-bot for Lai Jiangshan
2014-05-22 12:26           ` [tip:sched/core] sched: Fix hotplug vs. set_cpus_allowed_ptr() tip-bot for Lai Jiangshan
2014-05-22 22:02             ` Srivatsa S. Bhat

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=538E840D.2040300@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.com \
    --cc=davej@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sasha.levin@oracle.com \
    --cc=tglx@linutronix.de \
    --cc=tj@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).