From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Con Kolivas <kernel@kolivas.org>, Ingo Molnar <mingo@kernel.org>,
Alfred Chen <cchalpha@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org
Subject: Re: [lkp] [sched/core] 4fa5cd5245: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97
Date: Fri, 30 Sep 2016 12:35:49 +0200 [thread overview]
Message-ID: <20160930103549.GH5016@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160930015102.GB20189@yexl-desktop>
On Fri, Sep 30, 2016 at 09:51:02AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 4fa5cd5245b627db88c9ca08ae442373b02596b4 ("sched/core: Do not use smp_processor_id() with preempt enabled in smpboot_thread_fn()")
>
So its perfectly ok to use smp_processor_id() in preemptible context,
assuming the task is pinned to one cpu.
smpboot threads are per definition per-cpu threads, those are bound to a
specific CPU and affinity cannot be changed by userspace.
next prev parent reply other threads:[~2016-09-30 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 1:51 [lkp] [sched/core] 4fa5cd5245: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97 kernel test robot
2016-09-30 10:35 ` Peter Zijlstra [this message]
2016-10-04 8:06 ` [tip:sched/urgent] Revert "sched/core: Do not use smp_processor_id() with preempt enabled in smpboot_thread_fn()" tip-bot for Ingo Molnar
2016-10-04 8:22 ` Thomas Gleixner
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=20160930103549.GH5016@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cchalpha@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--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