From: Jeff Layton <jlayton@kernel.org>
To: Joshua Watt <jpewhacker@gmail.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Trond Myklebust <trondmy@kernel.org>, Anna Schumaker <anna@kernel.org>
Subject: Re: [PATCH] NFS: Fix state renewals missing after boot
Date: Thu, 09 Oct 2025 07:50:12 -0400 [thread overview]
Message-ID: <eb9a246727a9c9bfdc497b41ae2056c29df20349.camel@kernel.org> (raw)
In-Reply-To: <20251008230935.738405-1-JPEWhacker@gmail.com>
On Wed, 2025-10-08 at 17:09 -0600, Joshua Watt wrote:
> From: Joshua Watt <jpewhacker@gmail.com>
>
> Since the last renewal time was initialized to 0 and jiffies start
> counting at -5 minutes, any clients connected in the first 5 minutes
> after a reboot would have their renewal timer set to a very long
> interval. If the connection was idle, this would result in the client
> state timing out on the server and the next call to the server would
> return NFS4ERR_BADSESSION.
>
> Fix this by initializing the last renewal time to the current jiffies
> instead of 0.
>
> Signed-off-by: Joshua Watt <jpewhacker@gmail.com>
> ---
> fs/nfs/client.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/nfs/client.c b/fs/nfs/client.c
> index 4e3dcc157a83..96cdfeb26a90 100644
> --- a/fs/nfs/client.c
> +++ b/fs/nfs/client.c
> @@ -181,6 +181,7 @@ struct nfs_client *nfs_alloc_client(const struct nfs_client_initdata *cl_init)
> clp->cl_nconnect = cl_init->nconnect;
> clp->cl_max_connect = cl_init->max_connect ? cl_init->max_connect : 1;
> clp->cl_net = get_net_track(cl_init->net, &clp->cl_ns_tracker, GFP_KERNEL);
> + clp->cl_last_renewal = jiffies;
>
> #if IS_ENABLED(CONFIG_NFS_LOCALIO)
> seqlock_init(&clp->cl_boot_lock);
Nice catch!
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-10-09 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 23:09 [PATCH] NFS: Fix state renewals missing after boot Joshua Watt
2025-10-09 11:50 ` Jeff Layton [this message]
2025-10-09 21:16 ` Anna Schumaker
2025-10-09 21:48 ` [PATCH v2] NFS4: " Joshua Watt
2025-10-10 16:56 ` [PATCH] NFS: " kernel test robot
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=eb9a246727a9c9bfdc497b41ae2056c29df20349.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=jpewhacker@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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