[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJhGHyAFn96n8vW4z_cmXLCd4p1HfxQBLR-u81m8HipWRVsJZg@mail.gmail.com>
Date: Fri, 12 Jul 2024 16:52:52 +0800
From: Lai Jiangshan <jiangshanlai@...il.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@...el.com>
Cc: "jiangshan.ljs@...group.com" <jiangshan.ljs@...group.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Nikula, Jani" <jani.nikula@...el.com>,
"Saarinen, Jani" <jani.saarinen@...el.com>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@...el.com>
Subject: Re: Regression on linux-next (next-20240709)
Hello
On Fri, Jul 12, 2024 at 1:42 PM Borah, Chaitanya Kumar
> commit 1726a17135905e2d2773f18d47bd4e17dd26e1ed
> Author: Lai Jiangshan mailto:jiangshan.ljs@...group.com
> Date: Thu Jul 4 11:49:13 2024 +0800
>
> workqueue: Put PWQ allocation and WQ enlistment in the same lock C.S.
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>
> We could not revert the patch because of merge conflict but resetting to the parent of the commit seems to fix the issue
>
> Could you please check why the patch causes this regression and provide a fix if necessary?
It has been fixed and it is in wq/for-6.11.
https://lore.kernel.org/lkml/ZpASNBN0hpTVcjE-@slm.duckdns.org/
Thanks
Lai
Powered by blists - more mailing lists