From: Steven Rostedt <rostedt@goodmis.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Julia Cartwright <julia@ni.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG v4.14-rt] kernel BUG at /work/rt/stable-rt.git/kernel/sched/core.c:1639!
Date: Wed, 22 Aug 2018 12:17:49 -0400 [thread overview]
Message-ID: <20180822121749.5c4632d7@gandalf.local.home> (raw)
In-Reply-To: <1534660115.6187.4.camel@gmx.de>
On Sun, 19 Aug 2018 08:28:35 +0200
Mike Galbraith <efault@gmx.de> wrote:
> On Sat, 2018-08-18 at 15:13 +0200, Mike Galbraith wrote:
> > seems it has be something from the 4.17 cycle that went back to 4.14-
> > stable after 4.1[56]-stable trees went extinct.
>
> See ("sched/core: Require cpu_active() in select_task_rq(), for user tasks")
>
> Fix it like so?
>
> sched: Allow pinned user tasks to be awakened to the CPU they pinned
>
> Since 7af443ee16976, select_fallback_rq() will BUG() if the CPU to
> which a task has pinned itself and pinned becomes !cpu_active()
> while it slept. Serving a 10 megaton eviction notice is neither
> helpful nor required, the task will migrate when it can do so.
This seems to fix the issue that I was seeing. Thanks!
I'll add this to my repo as well.
-- Steve
>
> Signed-off-by: Mike Galbraith <efault@gmx.de>
> ---
> kernel/sched/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -980,7 +980,7 @@ static inline bool is_cpu_allowed(struct
> if (!cpumask_test_cpu(cpu, p->cpus_ptr))
> return false;
>
> - if (is_per_cpu_kthread(p))
> + if (is_per_cpu_kthread(p) || __migrate_disabled(p))
> return cpu_online(cpu);
>
> return cpu_active(cpu);
next prev parent reply other threads:[~2018-08-22 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 20:23 [BUG v4.14-rt] kernel BUG at /work/rt/stable-rt.git/kernel/sched/core.c:1639! Steven Rostedt
2018-08-18 10:29 ` Mike Galbraith
2018-08-18 13:13 ` Mike Galbraith
2018-08-19 6:28 ` Mike Galbraith
2018-08-22 16:17 ` Steven Rostedt [this message]
2018-08-22 16:33 ` Steven Rostedt
2018-08-29 14:00 ` Sebastian Andrzej Siewior
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=20180822121749.5c4632d7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).