From: "Michal Koutný" <mkoutny@suse.com>
To: Jing-Ting Wu <jing-ting.wu@mediatek.com>
Cc: Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
Zefan Li <lizefan.x@bytedance.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Shakeel Butt <shakeelb@google.com>,
wsd_upstream@mediatek.com, lixiong.liu@mediatek.com,
wenju.xu@mediatek.com, jonathan.jmchen@mediatek.com
Subject: Re: [Bug] race condition at rebind_subsystems()
Date: Tue, 19 Jul 2022 15:35:12 +0200 [thread overview]
Message-ID: <20220719133512.GD897@blackbody.suse.cz> (raw)
In-Reply-To: <d8f0bc5e2fb6ed259f9334c83279b4c011283c41.camel@mediatek.com>
On Mon, Jul 18, 2022 at 03:44:21PM +0800, Jing-Ting Wu <jing-ting.wu@mediatek.com> wrote:
> Accroding your description, is the following patch corrent?
Yes, this is what I meant (i.e. grace period before invalidating the
removed rstat_css_node).
> If the patch is correct, we will add this patch to our stability test.
> And we will continue to observe whether the problem is solved.
It'd be great to have such confirmation.
Thanks,
Michal
next prev parent reply other threads:[~2022-07-19 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 10:52 [Bug] race condition at rebind_subsystems() Jing-Ting Wu
2022-07-15 11:59 ` Michal Koutný
[not found] ` <20220715115938.GA8646-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2022-07-15 16:47 ` Tejun Heo
[not found] ` <YtGaP+e35DZYSQf0-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-07-18 7:44 ` Jing-Ting Wu
2022-07-19 13:35 ` Michal Koutný [this message]
[not found] ` <20220719133512.GD897-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2022-07-21 6:46 ` Jing-Ting Wu
[not found] ` <98d738ec5d7d32441f6e62278fff32201fd948de.camel-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2022-08-07 6:58 ` Jing-Ting Wu
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=20220719133512.GD897@blackbody.suse.cz \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jing-ting.wu@mediatek.com \
--cc=jonathan.jmchen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lixiong.liu@mediatek.com \
--cc=lizefan.x@bytedance.com \
--cc=matthias.bgg@gmail.com \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=wenju.xu@mediatek.com \
--cc=wsd_upstream@mediatek.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