From: Tejun Heo <tj@kernel.org>
To: Qais Yousef <qais.yousef@arm.com>
Cc: Qian Cai <cai@lca.pw>, Prateek Sood <prsood@codeaurora.org>,
Li Zefan <lizefan@huawei.com>,
cgroups@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Deadlock due to "cpuset: Make cpuset hotplug synchronous"
Date: Tue, 7 Apr 2020 09:35:20 -0400 [thread overview]
Message-ID: <20200407133520.GI162390@mtj.duckdns.org> (raw)
In-Reply-To: <20200407130725.jhtth3bneo33zex6@e107158-lin.cambridge.arm.com>
On Tue, Apr 07, 2020 at 02:07:26PM +0100, Qais Yousef wrote:
> On 04/06/20 10:34, Tejun Heo wrote:
> > On Mon, Apr 06, 2020 at 11:55:23AM +0100, Qais Yousef wrote:
> > > What would be the right approach to get a fix in then? We have been skipping
> > > this test for a while and we'd like to enable it but this failure is a
> > > blocking issue.
> >
> > Update the test so that it accounts for the async nature of the operation?
>
> With a sleep() between the hp ops and the read? Isn't this a nasty hack?
Some operations are just async. Why is that inherently wrong?
> I was just trying to find out what can be done for 5.7. But based on your
> response this is sadly a dead end. For no reason I can comprehend.
Because it's creating real issues while trying to address a non-real problem.
It's dumb. Fix the non-real part.
Thanks.
--
tejun
next prev parent reply other threads:[~2020-04-07 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 19:16 Qian Cai
2020-03-25 19:19 ` Tejun Heo
2020-03-26 10:15 ` Qais Yousef
2020-04-03 14:55 ` Tejun Heo
2020-04-06 10:55 ` Qais Yousef
2020-04-06 14:34 ` Tejun Heo
2020-04-07 13:07 ` Qais Yousef
2020-04-07 13:35 ` Tejun Heo [this message]
2020-04-02 2:00 ` Qian Cai
2020-04-03 14:54 ` Tejun Heo
2020-03-25 20:20 ` Peter Zijlstra
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=20200407133520.GI162390@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=cai@lca.pw \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=peterz@infradead.org \
--cc=prsood@codeaurora.org \
--cc=qais.yousef@arm.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
all inboxes | Powered by JetHome®