From: "rik.theys via Bugspray Bot" <bugbot@kernel.org>
To: anna@kernel.org, aglo@umich.edu, jlayton@kernel.org,
trondmy@kernel.org, linux-nfs@vger.kernel.org, cel@kernel.org
Subject: Re: warning in nfsd4_cb_done
Date: Mon, 24 Feb 2025 11:55:16 +0000 [thread overview]
Message-ID: <20250224-b219737c12-c39f21164cea@bugzilla.kernel.org> (raw)
In-Reply-To: <20250130-b219737c0-091f27de8b7a@bugzilla.kernel.org>
rik.theys writes via Kernel.org Bugzilla:
Hi,
We're currently running 6.12.13 with the following 4 patches on top:
1. 1b3e26a5ccbfc2f85bda1930cc278e313165e353: NFSD: fix decoding in nfs4_xdr_dec_cb_getattr
This patch went into 6.13-rc7, but I don't think it was CC'ed to stable?
I also don't see it in nfsd-6.12.y branch on https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/log
Is it not needed on 6.12?
2. cedfbb92cf97a6bff3d25633001d9c44442ee854: NFSD: fix hang in nfsd4_shutdown_callback
This one is now in 6.12.16
3. 99e98a2312c8d08fba60d548009c03e7cfb1bf6b: NFSD: Skip sending CB_RECALL_ANY when the backchannel isn't up
This one seems to have a CC: stable but I assume it's not yet there as it isn't included in the mainline kernel yet? Is it expected to be merged into 6.14-rcX, or will it have to wait for 6.15?
4. 4990d098433db18c854e75fb0f90d941eb7d479e: NFSD: Fix CB_GETATTR status fix
This one seems to be in 6.14-rc, but also doesn't have a CC: stable? It fixes 1b3e26a5ccbfc2f85bda1930cc278e313165e353 above.
Are there any plans to include these patches in the 6.12.y kernel?
Some of the patches mentioned above are in the nfsd-{fixes,testing,next} branches on https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git, but I don't know what all of these branches are used for. Is the nfsd-next branch what's expected to land in the next upstream kernel (6.15-rc1), or also the current rc kernels (6.14-rcX)?
What is the difference between the nfsd-testing and nfsd-fixes branch?
This kernel seems to be running stable for now, but it's too soon to conclude it fixes the issue that sometimes comes up. It does show the following kernel message sometimes:
rpc-srv/tcp: nfsd: sent 106256 when sending 131204 bytes - shutting down socket
I don't recall seeing this message with previous (6.11 and earlier) kernels. Does this message mean a single connection to a client was shut down? Is this a message we can ignore?
Regards,
Rik
View: https://bugzilla.kernel.org/show_bug.cgi?id=219737#c12
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-02-24 11:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 14:05 warning in nfsd4_cb_done rik.theys via Bugspray Bot
2025-01-30 14:10 ` Chuck Lever via Bugspray Bot
2025-01-30 15:08 ` Olga Kornievskaia
2025-01-30 15:20 ` Chuck Lever via Bugspray Bot
2025-01-30 15:20 ` Chuck Lever via Bugspray Bot
2025-01-30 15:55 ` Chuck Lever via Bugspray Bot
2025-01-30 14:20 ` rik.theys via Bugspray Bot
2025-02-04 13:30 ` rik.theys via Bugspray Bot
2025-02-04 13:30 ` Chuck Lever via Bugspray Bot
2025-02-10 15:03 ` Olga Kornievskaia
2025-02-10 16:35 ` Jeff Layton via Bugspray Bot
2025-02-10 15:45 ` Jeff Layton via Bugspray Bot
2025-02-10 16:45 ` Chuck Lever via Bugspray Bot
2025-02-24 11:55 ` rik.theys via Bugspray Bot [this message]
2025-02-24 12:20 ` Jeff Layton via Bugspray Bot
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=20250224-b219737c12-c39f21164cea@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=aglo@umich.edu \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@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