From: Mukesh Ojha <quic_mojha@quicinc.com> To: Tejun Heo <tj@kernel.org> Cc: 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> Subject: Re: Query regarding deadlock involving cgroup_threadgroup_rwsem and cpu_hotplug_lock Date: Fri, 12 Aug 2022 15:57:00 +0530 [thread overview] Message-ID: <dc0cff0e-b744-9d5d-e727-70d1c31b2a74@quicinc.com> (raw) In-Reply-To: <YuGTBLkFerUboctl@slm.duckdns.org> Hi Tejun, On 7/28/2022 1:03 AM, Tejun Heo wrote: > On Wed, Jul 20, 2022 at 08:05:03AM -1000, Tejun Heo wrote: >> On Wed, Jul 20, 2022 at 05:31:51PM +0530, Mukesh Ojha wrote: >>> Looks like these patches are the fixes. >>> >>> https://lore.kernel.org/all/YtDvN0wJ6CKaEPN8@slm.duckdns.org/#r >>> >>> Would let Tejun confirm this . >> >> Yeah, looks like the same issue. I'll write up a patch later this week / >> early next unless someone beats me to it. > > https://lore.kernel.org/lkml/20220705123705.764-1-xuewen.yan@unisoc.com/ is > the thread with the same issue. Let's follow up there. Since, i am not part of the above thread, is the reason i am commenting here. The original patch of yours [1] and the revert of [2] is fixing the issue and it is also confirmed here [3]. Can we get proper fix merge on your tree? [1] https://lore.kernel.org/lkml/YuGbYCfAG81mZBnN@slm.duckdns.org/ [2] https://lore.kernel.org/all/20220121101210.84926-1-zhangqiao22@huawei.com/ [3] https://lore.kernel.org/lkml/CAB8ipk-72V-bYRfL-VcSRSyXTeQqkBVj+1d5MHSVV5CTar9a0Q@mail.gmail.com/ -Mukesh > > Thanks. >
WARNING: multiple messages have this Message-ID (diff)
From: Mukesh Ojha <quic_mojha-jfJNa2p1gH1BDgjK7y7TUQ@public.gmane.org> To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Cc: 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 Subject: Re: Query regarding deadlock involving cgroup_threadgroup_rwsem and cpu_hotplug_lock Date: Fri, 12 Aug 2022 15:57:00 +0530 [thread overview] Message-ID: <dc0cff0e-b744-9d5d-e727-70d1c31b2a74@quicinc.com> (raw) In-Reply-To: <YuGTBLkFerUboctl-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org> Hi Tejun, On 7/28/2022 1:03 AM, Tejun Heo wrote: > On Wed, Jul 20, 2022 at 08:05:03AM -1000, Tejun Heo wrote: >> On Wed, Jul 20, 2022 at 05:31:51PM +0530, Mukesh Ojha wrote: >>> Looks like these patches are the fixes. >>> >>> https://lore.kernel.org/all/YtDvN0wJ6CKaEPN8-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org/#r >>> >>> Would let Tejun confirm this . >> >> Yeah, looks like the same issue. I'll write up a patch later this week / >> early next unless someone beats me to it. > > https://lore.kernel.org/lkml/20220705123705.764-1-xuewen.yan-1tVvrHeaX6nQT0dZR+AlfA@public.gmane.org/ is > the thread with the same issue. Let's follow up there. Since, i am not part of the above thread, is the reason i am commenting here. The original patch of yours [1] and the revert of [2] is fixing the issue and it is also confirmed here [3]. Can we get proper fix merge on your tree? [1] https://lore.kernel.org/lkml/YuGbYCfAG81mZBnN-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org/ [2] https://lore.kernel.org/all/20220121101210.84926-1-zhangqiao22-hv44wF8Li93QT0dZR+AlfA@public.gmane.org/ [3] https://lore.kernel.org/lkml/CAB8ipk-72V-bYRfL-VcSRSyXTeQqkBVj+1d5MHSVV5CTar9a0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org/ -Mukesh > > Thanks. >
next prev parent reply other threads:[~2022-08-12 10:27 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 [this message] 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 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=dc0cff0e-b744-9d5d-e727-70d1c31b2a74@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=peterz@infradead.org \ --cc=steven.price@arm.com \ --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: 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.