From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Schspa Shi <schspa@gmail.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com
Cc: linux-kernel@vger.kernel.org, zhaohui.shi@horizon.ai
Subject: Re: [PATCH v7 1/2] sched/rt: fix bad task migration for rt tasks
Date: Fri, 26 Aug 2022 20:45:54 +0200 [thread overview]
Message-ID: <43de1f15-42cf-45ea-db5c-30de976a6828@arm.com> (raw)
In-Reply-To: <20220713134823.95141-1-schspa@gmail.com>
On 13/07/2022 15:48, Schspa Shi wrote:
> Commit 95158a89dd50 ("sched,rt: Use the full cpumask for balancing")
> allow find_lock_lowest_rq to pick a task with migration disabled.
> This commit is intended to push the current running task on this CPU
> away.
>
> There is a race scenario, which allows a migration disabled task to
> be migrated to another CPU.
>
> When there is a RT task with higher priority, rt sched class was
> intended to migrate higher priority task to lowest rq via push_rt_tasks,
> this BUG will happen here.
^^^
You mean the warning in set_task_cpu()?
> With the system running on PREEMPT_RT, rt_spin_lock will disable
> migration, this will make the problem easier to reproduce.
>
> I have seen this crash on PREEMPT_RT, from the logs, there is a race
^^^^^
?
We still talking about the set_task_cpu() warning, right?
[...]
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
You should carry the Reviewed-by:'s you got in previous versions.
next prev parent reply other threads:[~2022-08-26 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 13:48 [PATCH v7 1/2] sched/rt: fix bad task migration for rt tasks Schspa Shi
2022-07-13 13:48 ` [PATCH v7 2/2] sched/rt: Trying to push current task when target disable migrating Schspa Shi
2022-08-26 18:46 ` Dietmar Eggemann
2022-08-28 15:54 ` Schspa Shi
2022-08-24 6:04 ` [PATCH v7 1/2] sched/rt: fix bad task migration for rt tasks Schspa Shi
2022-08-26 18:45 ` Dietmar Eggemann [this message]
2022-08-28 15:45 ` Schspa Shi
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=43de1f15-42cf-45ea-db5c-30de976a6828@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=schspa@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=zhaohui.shi@horizon.ai \
/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