From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>,
Alexey Klimov <aklimov@redhat.com>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
yury.norov@gmail.com, tglx@linutronix.de, jobaker@redhat.com,
audralmitchel@gmail.com, arnd@arndb.de,
gregkh@linuxfoundation.org, rafael@kernel.org, tj@kernel.org,
lizefan@huawei.com, qais.yousef@arm.com, hannes@cmpxchg.org,
klimov.linux@gmail.com
Subject: Re: [RFC][PATCH] cpu/hotplug: wait for cpuset_hotplug_work to finish on cpu online
Date: Tue, 08 Dec 2020 21:40:57 -0500 [thread overview]
Message-ID: <87k0tritvq.fsf@oracle.com> (raw)
In-Reply-To: <20201207083827.GD3040@hirez.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> writes:
>> The nature of this bug is also described here (with different consequences):
>> https://lore.kernel.org/lkml/20200211141554.24181-1-qais.yousef@arm.com/
>
> Yeah, pesky deadlocks.. someone was going to try again.
I dug up the synchronous patch
https://lore.kernel.org/lkml/1579878449-10164-1-git-send-email-prsood@codeaurora.org/
but surprisingly wasn't able to reproduce the lockdep splat from
https://lore.kernel.org/lkml/F0388D99-84D7-453B-9B6B-EEFF0E7BE4CC@lca.pw/
even though I could hit it a few weeks ago. I'm going to try to mess
with it later, but don't let me hold this up.
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Jordan <daniel.m.jordan-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Alexey Klimov <aklimov-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yury.norov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
jobaker-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
audralmitchel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
qais.yousef-5wv7dgnIgG8@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
klimov.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [RFC][PATCH] cpu/hotplug: wait for cpuset_hotplug_work to finish on cpu online
Date: Tue, 08 Dec 2020 21:40:57 -0500 [thread overview]
Message-ID: <87k0tritvq.fsf@oracle.com> (raw)
In-Reply-To: <20201207083827.GD3040-Nxj+rRp3nVydTX5a5knrm8zTDFooKrT+cvkQGrU6aU0@public.gmane.org>
Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> writes:
>> The nature of this bug is also described here (with different consequences):
>> https://lore.kernel.org/lkml/20200211141554.24181-1-qais.yousef-5wv7dgnIgG8@public.gmane.org/
>
> Yeah, pesky deadlocks.. someone was going to try again.
I dug up the synchronous patch
https://lore.kernel.org/lkml/1579878449-10164-1-git-send-email-prsood-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org/
but surprisingly wasn't able to reproduce the lockdep splat from
https://lore.kernel.org/lkml/F0388D99-84D7-453B-9B6B-EEFF0E7BE4CC-J5quhbR+WMc@public.gmane.org/
even though I could hit it a few weeks ago. I'm going to try to mess
with it later, but don't let me hold this up.
next prev parent reply other threads:[~2020-12-09 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 17:14 [RFC][PATCH] cpu/hotplug: wait for cpuset_hotplug_work to finish on cpu online Alexey Klimov
2020-12-03 17:14 ` Alexey Klimov
2020-12-07 8:38 ` Peter Zijlstra
2020-12-07 8:38 ` Peter Zijlstra
2020-12-09 2:40 ` Daniel Jordan [this message]
2020-12-09 2:40 ` Daniel Jordan
2021-01-15 3:21 ` Daniel Jordan
2021-01-15 3:21 ` Daniel Jordan
2021-01-19 16:52 ` Alexey Klimov
2021-01-19 16:52 ` Alexey Klimov
2021-01-21 2:09 ` Daniel Jordan
2020-12-09 2:09 ` Daniel Jordan
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=87k0tritvq.fsf@oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=aklimov@redhat.com \
--cc=arnd@arndb.de \
--cc=audralmitchel@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=jobaker@redhat.com \
--cc=klimov.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=yury.norov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.