From: Mike Galbraith <efault@gmx.de>
To: Jeff Layton <jlayton@kernel.org>, Dai Ngo <dai.ngo@oracle.com>,
chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] NFSD: register/unregister of nfsd-client shrinker at nfsd startup/shutdown time
Date: Wed, 11 Jan 2023 16:08:03 +0100 [thread overview]
Message-ID: <67f3e5de50d1e21dba2ba7484f9df55c04bdabf5.camel@gmx.de> (raw)
In-Reply-To: <23f1fda9f550a73182cafc140bb8dfb9af2ea874.camel@kernel.org>
On Wed, 2023-01-11 at 09:34 -0500, Jeff Layton wrote:
>
> I suspect that this patch is probably enough to fix the problem that
> Mike is hitting. Perhaps we should mark this for stable after revising
> the changelog?
>
> Mike, would you be able to test this patch and see whether it fixes the
> shrinker oopses you've been hitting? It's also commit a77ce15ca9cb10 in
> Chuck's git tree.
Yup, all better.
-Mike
prev parent reply other threads:[~2023-01-11 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 6:43 [PATCH 1/1] NFSD: register/unregister of nfsd-client shrinker at nfsd startup/shutdown time Dai Ngo
2023-01-10 10:24 ` Jeff Layton
2023-01-10 17:25 ` dai.ngo
2023-01-10 15:34 ` Chuck Lever III
2023-01-11 14:34 ` Jeff Layton
2023-01-11 15:08 ` Mike Galbraith [this message]
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=67f3e5de50d1e21dba2ba7484f9df55c04bdabf5.camel@gmx.de \
--to=efault@gmx.de \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@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