From: Mike Galbraith <efault@gmx.de>
To: dai.ngo@oracle.com, Chuck Lever III <chuck.lever@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: regression: nfs mount (even idle) eventually hangs server
Date: Fri, 23 Dec 2022 14:05:29 +0100 [thread overview]
Message-ID: <b748cbd9db3a5ac06fe48235ed2a1d110261cafa.camel@gmx.de> (raw)
In-Reply-To: <ae11915e-9253-4049-e9a6-31432679d27c@oracle.com>
On Fri, 2022-12-23 at 04:02 -0800, dai.ngo@oracle.com wrote:
> Hi Mike,
>
> I think the problem is the nfsd4_state_shrinker_worker is being
> scheduled to run multiple times. This trigger the WARN_ON_ONCE
> in __queue_delayed_work.
>
> Could you try the attached patch to see if it fixes this problem.
> I tried to reproduce it on my test VMs but no success so I can't
> verify the patch.
> >
That was a nogo.
bart:/root # grep WARNING: netconsole.log
[ 1030.364594] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1655 __queue_delayed_work+0x6a/0x90
[ 1030.364970] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1657 __queue_delayed_work+0x5a/0x90
[ 1030.365315] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.365666] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.365992] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.366333] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.366669] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.366995] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.367317] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.367636] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
[ 1030.367962] WARNING: CPU: 4 PID: 79 at kernel/workqueue.c:1500 __queue_work+0x33b/0x3d0
next prev parent reply other threads:[~2022-12-23 13:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 8:59 regression: nfs mount (even idle) eventually hangs server Mike Galbraith
2022-12-21 9:56 ` Mike Galbraith
2022-12-22 3:42 ` Mike Galbraith
2022-12-22 4:14 ` Mike Galbraith
2022-12-22 4:28 ` Chuck Lever III
2022-12-22 4:44 ` Mike Galbraith
2022-12-22 13:30 ` Mike Galbraith
2022-12-22 14:21 ` Chuck Lever III
2022-12-23 4:41 ` Mike Galbraith
2022-12-23 6:28 ` Mike Galbraith
2022-12-23 12:02 ` dai.ngo
2022-12-23 13:05 ` Mike Galbraith [this message]
2023-01-09 0:50 ` dai.ngo
2023-01-09 2:41 ` Mike Galbraith
2023-01-09 6:34 ` dai.ngo
2022-12-22 11:19 ` regression: nfs mount (even idle) eventually hangs server #forregzbot Thorsten Leemhuis
2023-02-17 12:45 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-01-05 14:14 ` summary: regression: nfs mount (even idle) eventually hangs server Mike Galbraith
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=b748cbd9db3a5ac06fe48235ed2a1d110261cafa.camel@gmx.de \
--to=efault@gmx.de \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).