From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Lai Jiangshan <jiangshanlai@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@lists.01.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] workqueue: Don't double assign worker->sleeping
Date: Wed, 1 Apr 2020 15:03:46 +0200 [thread overview]
Message-ID: <20200401130346.e7cdsqgxppa6ohje@linutronix.de> (raw)
In-Reply-To: <CAJhGHyBS9Z=x-X2Bxzbic2sfqj=STqr+K8Tgu1UfYMQDm6MtBg@mail.gmail.com>
On 2020-04-01 11:44:06 [+0800], Lai Jiangshan wrote:
> On Wed, Apr 1, 2020 at 11:22 AM Lai Jiangshan <jiangshanlai@gmail.com> wrote:
> >
> > Hello
Hi Lai,
…
> > 2) wq_worker_running() can be interrupted(async-page-faulted in virtual machine)
> > and nr_running would be decreased twice.
>
> would be *increased* twice
>
> I just saw the V2 patch, this issue is not listed, but need to be fixed too.
| void wq_worker_running(struct task_struct *task)
| {
| struct worker *worker = kthread_data(task);
|
| if (!worker->sleeping)
| return;
| if (!(worker->flags & WORKER_NOT_RUNNING))
| atomic_inc(&worker->pool->nr_running);
*0
| worker->sleeping = 0;
*1
| }
So an interrupt
- before *0, the preempting caller drop early in wq_worker_sleeping(), only one
atomic_inc()
- after *1, the preempting task will invoke wq_worker_sleeping() and do
dec() + inc().
What did I miss here?
Sebastian
next prev parent reply other threads:[~2020-04-01 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 7:43 6d25be5782 ("sched/core, workqueues: Distangle worker .."): [ 52.816697] WARNING: CPU: 0 PID: 14 at kernel/workqueue.c:882 wq_worker_sleeping kernel test robot
2020-03-27 17:53 ` [PATCH] workqueue: Don't double assign worker->sleeping Sebastian Andrzej Siewior
2020-03-27 23:29 ` [PATCH v2] workqueue: Remove the warning in wq_worker_sleeping() Sebastian Andrzej Siewior
2020-04-03 14:53 ` Tejun Heo
2020-04-03 19:29 ` Sebastian Andrzej Siewior
2020-04-03 17:45 ` Daniel Jordan
2020-04-03 18:25 ` Sebastian Andrzej Siewior
2020-04-03 19:05 ` Daniel Jordan
2020-04-01 3:22 ` [PATCH] workqueue: Don't double assign worker->sleeping Lai Jiangshan
2020-04-01 3:44 ` Lai Jiangshan
2020-04-01 13:03 ` Sebastian Andrzej Siewior [this message]
2020-04-02 0:07 ` Lai Jiangshan
2020-04-02 7:29 ` Sebastian Andrzej Siewior
2020-04-08 12:20 ` [tip: sched/urgent] workqueue: Remove the warning in wq_worker_sleeping() tip-bot2 for 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=20200401130346.e7cdsqgxppa6ohje@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®