Re: commit 0c4f1c02d27a880b cause a deadlock issue

[Greg KH <gregkh@linuxfoundation.org>]

On Fri, Apr 03, 2026 at 12:44:48PM +0000, Korenblit, Miriam Rachel wrote:
> 
> 
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Friday, April 3, 2026 2:27 PM
> > To: He, Guocai (CN) <Guocai.He.CN@windriver.com>
> > Cc: Thorsten Leemhuis <regressions@leemhuis.info>; Korenblit, Miriam Rachel
> > <miriam.rachel.korenblit@intel.com>; Berg, Johannes
> > <johannes.berg@intel.com>; Friend <netdev@vger.kernel.org>; Linux kernel
> > regressions list <regressions@lists.linux.dev>
> > Subject: Re: commit 0c4f1c02d27a880b cause a deadlock issue
> > 
> > On Fri, Apr 03, 2026 at 11:08:46AM +0000, He, Guocai (CN) wrote:
> > > No, The mainline have no this issue.
> > > The changes of 0c4f1c02d27a880b is not in mainline.
> > 
> > That does not make sense, that commit is really commit e1696c8bd005
> > ("wifi: cfg80211: stop NAN and P2P in cfg80211_leave") which is in all of the
> > following releases:
> > 	5.10.252 5.15.202 6.1.165 6.6.128 6.12.75 6.18.14 6.19.4 7.0-rc1
> > 
> > confused,
> 
> The change is indeed in mainline, but the locking situation in mainline is totally different
> (that mutex does not even exist there)
> Therefore, the issue is not supposed to happen in mainline.

Ok, does that commit now need to be reverted from some of the stable
branches?  If so, which ones?

thanks,

greg k-h