Received-SPF: pass (google.com: domain of linux-kernel+bounces-154041-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Mon, 22 Apr 2024 16:23:15 -0500
From: Bjorn Andersson <andersson@kernel.org>
To: Tejun Heo <tj@kernel.org>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>, 
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug 218665 - nohz_full=0 prevents kernel from booting
Message-ID: <zyu6awsydy5ypb7tn7wzgumxbh4qrw2g5luc3w6trzlnmtu64v@c4knsvtk532w>
References: <5be248c6-cdda-4d2e-8fae-30fc2cc124c0@leemhuis.info>
 <enqg6mcuhvff7gujjbapdiclicl3z6f2vnggcsg65pexipyr3o@4men5fhyt3vb>
 <28c84b3b-f68f-4f45-8da1-9c3f9a342509@leemhuis.info>
 <7kugx5ivbplwwrcq5zp37djtpakl55b3pfy36gpbsbcx43dpcs@uheu6iv7gm7h>
 <81149f18-0132-4ace-8c71-1b75790a88e4@leemhuis.info>
 <Zh8H_vG2dQLOjoIB@slm.duckdns.org>
 <51942e58-a5a3-4dcd-80c1-6735c7b5cc1e@leemhuis.info>
 <ZiCAXq-jS1Z6vgCK@slm.duckdns.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZiCAXq-jS1Z6vgCK@slm.duckdns.org>

On Wed, Apr 17, 2024 at 04:07:26PM -1000, Tejun Heo wrote:
> Hello, Thorsten.
> 
> On Wed, Apr 17, 2024 at 07:48:33AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > > Can you elaborate why Bjorn's case is different?
> > 
> > Well "not booting at all when using 'nohz_full=0'"[as reported two
> > times] and "I start neovim, send SIGSTOP (i.e. ^Z) to it, start another
> > neovim instance and upon sending SIGSTOP to that instance all of
> > userspace locks up - 100% reproducible."[while no 'nohz_full=0' in use]
> > at least on the first sight to and outsider sound a lot like different
> > problems to me -- but of course that impression might be wrong and you
> > know better about these things.
> 
> You are right. That is very different.
> 
> > > I was assuming it was the
> > > same problem and that Oleg's fixes would address the issue.
> > 
> > Bjorn, could you give it a try?
> 
> Yeah, I'm curious whether it's just a different symptom of the same problem.
> 

Sorry for the late reply, had to step back to v6.8 on my work machine
and didn't retry this in a timely manner.

I've now confirmed that my problem with Neovim was resolved in v6.9-rc3,
through the introduction of:
73eaa2b58349 ("io_uring: use private workqueue for exit work")

Regards,
Bjorn