From: Frederic Weisbecker <fweisbec@gmail.com>
To: riel@redhat.com, peterz@infradead.org, wanpeng.li@hotmail.com,
torvalds@linux-foundation.org, xiaolong.ye@intel.com,
mingo@kernel.org, tglx@linutronix.de, hpa@zytor.com,
lcapitulino@redhat.com, linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/urgent] sched/cputime: Don't use smp_processor_id() in preemptible context
Date: Mon, 17 Jul 2017 04:31:14 +0200 [thread overview]
Message-ID: <20170717023112.GA10020@lerouge> (raw)
In-Reply-To: <tip-0e4097c3354e2f5a5ad8affd9dc7f7f7d00bb6b9@git.kernel.org>
On Fri, Jul 14, 2017 at 02:10:14AM -0700, tip-bot for Wanpeng Li wrote:
> Commit-ID: 0e4097c3354e2f5a5ad8affd9dc7f7f7d00bb6b9
> Gitweb: http://git.kernel.org/tip/0e4097c3354e2f5a5ad8affd9dc7f7f7d00bb6b9
> Author: Wanpeng Li <wanpeng.li@hotmail.com>
> AuthorDate: Sun, 9 Jul 2017 00:40:28 -0700
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Fri, 14 Jul 2017 10:27:15 +0200
>
> sched/cputime: Don't use smp_processor_id() in preemptible context
>
> Recent kernels trigger this warning:
>
> BUG: using smp_processor_id() in preemptible [00000000] code: 99-trinity/181
> caller is debug_smp_processor_id+0x17/0x19
> CPU: 0 PID: 181 Comm: 99-trinity Not tainted 4.12.0-01059-g2a42eb9 #1
> Call Trace:
> dump_stack+0x82/0xb8
> check_preemption_disabled()
> debug_smp_processor_id()
> vtime_delta()
> task_cputime()
> thread_group_cputime()
> thread_group_cputime_adjusted()
> wait_consider_task()
> do_wait()
> SYSC_wait4()
> do_syscall_64()
> entry_SYSCALL64_slow_path()
>
> As Frederic pointed out:
>
> | Although those sched_clock_cpu() things seem to only matter when the
> | sched_clock() is unstable. And that stability is a condition for nohz_full
> | to work anyway. So probably sched_clock() alone would be enough.
>
> This patch fixes it by replacing sched_clock_cpu() with sched_clock() to
> avoid calling smp_processor_id() in a preemptible context.
>
> Reported-by: Xiaolong Ye <xiaolong.ye@intel.com>
> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Luiz Capitulino <lcapitulino@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Rik van Riel <riel@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Link: http://lkml.kernel.org/r/1499586028-7402-1-git-send-email-wanpeng.li@hotmail.com
> [ Prettified the changelog. ]
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
Thanks! The patch looks good!
prev parent reply other threads:[~2017-07-17 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 7:40 [PATCH v3] sched/cputime: Fix using smp_processor_id() in preemptible Wanpeng Li
2017-07-14 6:49 ` Wanpeng Li
[not found] ` <CAJzB8QHu3Jfy6+H_qxJd83696qsLBnJp0ke55iaJ-JMqZ0TAGQ@mail.gmail.com>
2017-07-20 22:33 ` Paul McKenney
2017-07-14 9:10 ` [tip:sched/urgent] sched/cputime: Don't use smp_processor_id() in preemptible context tip-bot for Wanpeng Li
2017-07-17 2:31 ` Frederic Weisbecker [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=20170717023112.GA10020@lerouge \
--to=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=wanpeng.li@hotmail.com \
--cc=xiaolong.ye@intel.com \
/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