From: Mike Galbraith <efault@gmx.de>
To: Chuck Lever III <chuck.lever@oracle.com>, Dai Ngo <dai.ngo@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: Thu, 22 Dec 2022 14:30:13 +0100 [thread overview]
Message-ID: <e51b8b218f18abe00ec76eb911d5b5b5af02f79b.camel@gmx.de> (raw)
In-Reply-To: <36902a3dd6ee1a8656548ff5b5eadb88245e2799.camel@gmx.de>
Quoting previous mail for context.
On Thu, 2022-12-22 at 05:14 +0100, Mike Galbraith wrote:
> On Thu, 2022-12-22 at 04:42 +0100, Mike Galbraith wrote:
> > On Wed, 2022-12-21 at 10:56 +0100, Mike Galbraith wrote:
> > > > 6.1 didn't reproduce either, so it would appear to be a merge window bug.
> >
> > Ah, not true, turning evolution loose in nfs mounted home and letting
> > it refresh mailboxes while desktop box was kept busy jammed up 6.1.0 in
> > fairly short order.
>
> Well crap. That was _not_ virgin 6.1.0 after all, it was 6.1.0 with...
>
> 44df6f439a17 NFSD: add delegation reaper to react to low memory condition
> 3959066b697b NFSD: add support for sending CB_RECALL_ANY
> a1049eb47f20 NFSD: refactoring courtesy_client_reaper to a generic low memory shrinker
>
> ...applied from poking about yesterday. I had given up on those as
> culprit, and intended to pop them off and rebuild, but they were in
> fact in the booted kernel. Oh well, booboo could have a bright side.
I let my desktop box play server/space-heater for a long test session
of 6.1 with and without the above series: with, box bricked 3 times in
~5 hours, without, 0 bricks in ~6 hours. Box says woof -> duck ;-)
Given the similarity you mentioned, I wonder if my bug is perhaps your
sneaky bug rendered somewhat less sneaky by that series? One can hope.
-Mike
next prev parent reply other threads:[~2022-12-22 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65ed34338c69cb034295f2c9cbe0af684d65d30f.camel@gmx.de>
2022-12-21 9:56 ` regression: nfs mount (even idle) eventually hangs server 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 [this message]
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
2023-01-09 0:50 ` dai.ngo
2023-01-09 2:41 ` Mike Galbraith
2023-01-09 6:34 ` dai.ngo
2023-01-05 14:14 ` summary: " 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=e51b8b218f18abe00ec76eb911d5b5b5af02f79b.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