From: Mukesh Ojha <quic_mojha@quicinc.com> To: "Michal Koutný" <mkoutny@suse.com>, "Xuewen Yan" <xuewen.yan94@gmail.com> Cc: Tejun Heo <tj@kernel.org>, Imran Khan <imran.f.khan@oracle.com>, <lizefan.x@bytedance.com>, <hannes@cmpxchg.org>, <tglx@linutronix.de>, <steven.price@arm.com>, <peterz@infradead.org>, <cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Zhao Gongyi <zhaogongyi@huawei.com>, Zhang Qiao <zhangqiao22@huawei.com> Subject: Re: Query regarding deadlock involving cgroup_threadgroup_rwsem and cpu_hotplug_lock Date: Mon, 15 Aug 2022 16:29:24 +0530 [thread overview] Message-ID: <f584fecd-6ca4-4ab0-763d-2ed219009c61@quicinc.com> (raw) In-Reply-To: <20220815093934.GA29323@blackbody.suse.cz> On 8/15/2022 3:09 PM, Michal Koutný wrote: > On Mon, Aug 15, 2022 at 05:25:52PM +0800, Xuewen Yan <xuewen.yan94@gmail.com> wrote: >> Your means is that the problem should be fixed by [1]+[2]'s revert ? > > I understood that was already the combination you had tested. > You write in [T] that [1] alone causes (another) deadlock and therefore > the revert of [2] was suggested. > >> I just tested the case which reverted the [2]. Need I test with [1] and [2]? > > It'd be better (unless you haven't already :-), my reasoning is for the > [1]+[2] combo. Feel free to add my Reported-and-tested-by: Mukesh Ojha <quic_mojha@quicinc.com> -Mukesh > > Thanks, > Michal > > [T] https://lore.kernel.org/r/CAB8ipk_gCLtvEahsp2DvPJf4NxRsM8WCYmmH=yTd7zQE+81_Yg@mail.gmail.com/
WARNING: multiple messages have this Message-ID (diff)
From: Mukesh Ojha <quic_mojha-jfJNa2p1gH1BDgjK7y7TUQ@public.gmane.org> To: "Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>, "Xuewen Yan" <xuewen.yan94-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Imran Khan <imran.f.khan-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>, lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org, hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org, tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org, steven.price-5wv7dgnIgG8@public.gmane.org, peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Zhao Gongyi <zhaogongyi-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>, Zhang Qiao <zhangqiao22-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> Subject: Re: Query regarding deadlock involving cgroup_threadgroup_rwsem and cpu_hotplug_lock Date: Mon, 15 Aug 2022 16:29:24 +0530 [thread overview] Message-ID: <f584fecd-6ca4-4ab0-763d-2ed219009c61@quicinc.com> (raw) In-Reply-To: <20220815093934.GA29323-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org> On 8/15/2022 3:09 PM, Michal Koutný wrote: > On Mon, Aug 15, 2022 at 05:25:52PM +0800, Xuewen Yan <xuewen.yan94-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> Your means is that the problem should be fixed by [1]+[2]'s revert ? > > I understood that was already the combination you had tested. > You write in [T] that [1] alone causes (another) deadlock and therefore > the revert of [2] was suggested. > >> I just tested the case which reverted the [2]. Need I test with [1] and [2]? > > It'd be better (unless you haven't already :-), my reasoning is for the > [1]+[2] combo. Feel free to add my Reported-and-tested-by: Mukesh Ojha <quic_mojha-jfJNa2p1gH1BDgjK7y7TUQ@public.gmane.org> -Mukesh > > Thanks, > Michal > > [T] https://lore.kernel.org/r/CAB8ipk_gCLtvEahsp2DvPJf4NxRsM8WCYmmH=yTd7zQE+81_Yg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org/
next prev parent reply other threads:[~2022-08-15 11:01 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <8245b710-8acb-d8e6-7045-99a5f71dad4e@oracle.com> 2022-07-20 2:38 ` Query regarding deadlock involving cgroup_threadgroup_rwsem and cpu_hotplug_lock Imran Khan 2022-07-20 3:27 ` Imran Khan 2022-07-20 3:27 ` Imran Khan 2022-07-20 11:06 ` Mukesh Ojha 2022-07-20 11:06 ` Mukesh Ojha 2022-07-20 12:01 ` Mukesh Ojha 2022-07-20 12:01 ` Mukesh Ojha 2022-07-20 18:05 ` Tejun Heo 2022-07-20 18:05 ` Tejun Heo 2022-07-27 19:33 ` Tejun Heo 2022-07-27 19:33 ` Tejun Heo 2022-08-12 10:27 ` Mukesh Ojha 2022-08-12 10:27 ` Mukesh Ojha 2022-08-15 9:05 ` Michal Koutný 2022-08-15 9:25 ` Xuewen Yan 2022-08-15 9:25 ` Xuewen Yan 2022-08-15 9:39 ` Michal Koutný 2022-08-15 9:39 ` Michal Koutný 2022-08-15 10:59 ` Mukesh Ojha [this message] 2022-08-15 10:59 ` Mukesh Ojha 2022-08-15 23:27 ` [PATCH cgroup/for-6.0-fixes] cgroup: Fix threadgroup_rwsem <-> cpus_read_lock() deadlock Tejun Heo 2022-08-15 23:27 ` Tejun Heo 2022-08-16 20:20 ` Imran Khan 2022-08-16 20:20 ` Imran Khan 2022-08-17 6:55 ` Xuewen Yan 2022-08-17 6:55 ` Xuewen Yan 2022-08-17 17:40 ` Tejun Heo 2022-08-17 17:40 ` Tejun Heo
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=f584fecd-6ca4-4ab0-763d-2ed219009c61@quicinc.com \ --to=quic_mojha@quicinc.com \ --cc=cgroups@vger.kernel.org \ --cc=hannes@cmpxchg.org \ --cc=imran.f.khan@oracle.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lizefan.x@bytedance.com \ --cc=mkoutny@suse.com \ --cc=peterz@infradead.org \ --cc=steven.price@arm.com \ --cc=tglx@linutronix.de \ --cc=tj@kernel.org \ --cc=xuewen.yan94@gmail.com \ --cc=zhangqiao22@huawei.com \ --cc=zhaogongyi@huawei.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: linkBe 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.