From: Chuck Lever III <chuck.lever@oracle.com>
To: email200202 <email200202@yahoo.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
"kernel@gentoo.org" <kernel@gentoo.org>,
linux-stable <stable@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [REGRESSION] After kernel upgrade 6.1.70 to 6.1.71, the computer hangs during shutdown
Date: Thu, 11 Jan 2024 14:05:52 +0000 [thread overview]
Message-ID: <1FAB3DFD-1CEA-4E7E-BF2F-12755F511A98@oracle.com> (raw)
In-Reply-To: <bbfe6944-a7f0-46f5-8a30-79eccf84664d@yahoo.com>
> On Jan 11, 2024, at 8:58 AM, email200202 <email200202@yahoo.com> wrote:
>
> Hi Greg
>
> Here is the test results for the latest versions of 6.6.x and 6.7.x available in Gentoo portage
>
> 1- Stopping NFS service failed but, unlike 6.1.x, it did NOT hang.
>
> # uname -r
> 6.6.11-gentoo
> # /etc/init.d/nfs stop
> * Stopping NFS mountd ... [ ok ]
> * Stopping NFS daemon ...
> * start-stop-daemon: 8 process(es) refused to stop [ !! ]
> * Unexporting NFS directories ... [ ok ]
> * ERROR: nfs failed to stop
> # /etc/init.d/nfs start
> * WARNING: nfs has already been started
>
>
> # uname -r
> 6.7.0-gentoo
> # /etc/init.d/nfs stop
> * Stopping NFS mountd ... [ ok ]
> * Stopping NFS daemon ...
> * start-stop-daemon: 8 process(es) refused to stop [ !! ]
> * Unexporting NFS directories ... [ ok ]
> * ERROR: nfs failed to stop
> # /etc/init.d/nfs start
> * WARNING: nfs has already been started
>
> 2- Shutdown didn't hang in both of them
>
> Best regards
> John G
>
> On 11/1/24 21:21, Greg KH wrote:
>> On Thu, Jan 11, 2024 at 09:10:39PM +1100, email200202 wrote:
>>> Hi Greg
>>>
>>> I'm sorry. This my first kernel report.
>>>
>>> I didn't test 6.6.x and 6.7.x. I use only 6.1.x.
>> Can you do so?
>>
>> thanks,
>>
>> greg k-h
I haven't seen emails before this one. But here are the only
three new NFSD commits in v6.1.71:
f9a01938e079 NFSD: fix possible oops when nfsd/pool_stats is closed.
bb4f791cb2de nfsd: call nfsd_last_thread() before final nfsd_put()
03d68ffc48b9 nfsd: separate nfsd_last_thread() from nfsd_put()
And the latter two are directly related to NFSD shut down.
--
Chuck Lever
next prev parent reply other threads:[~2024-01-11 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58ac38ae-4d64-4a53-81e0-35785961c41c.ref@yahoo.com>
2024-01-11 8:20 ` [REGRESSION] After kernel upgrade 6.1.70 to 6.1.71, the computer hangs during shutdown email200202
2024-01-11 9:30 ` Greg KH
2024-01-11 10:10 ` email200202
2024-01-11 10:21 ` Greg KH
2024-01-11 13:58 ` email200202
2024-01-11 14:05 ` Chuck Lever III [this message]
2024-01-11 17:26 ` Jeff Layton
2024-01-13 9:35 ` Greg KH
2024-01-13 9:39 ` Greg KH
2024-01-19 10:13 ` Linux regression tracking #update (Thorsten Leemhuis)
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=1FAB3DFD-1CEA-4E7E-BF2F-12755F511A98@oracle.com \
--to=chuck.lever@oracle.com \
--cc=email200202@yahoo.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@gentoo.org \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox