public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lubos Rendek <l.rendek@proxmox.com>
Subject: applied: [PATCH kernel] fix #8121: cherry-pick fix for hanging NFSv4.2 server-side copy
Date: Fri,  6 Nov 2026 20:32:41 +0100	[thread overview]
Message-ID: <179399355960.121441.18292885359979936185.b4-ty@b4> (raw)
In-Reply-To: <20261104004848.29637-1-l.rendek@proxmox.com>

On Wed, 04 Nov 2026 11:48:48 +1100, Lubos Rendek wrote:
> Since 7.0.14-20, an NFSv4.2 server-side copy between two exports of an
> NFS server running our kernel never completes: nfsd sends the CB_OFFLOAD
> callback with an all-zero stateid, so the client cannot match it to its
> pending COPY and cp(1) waits forever, even though the data is already
> complete on the server.
> 
> Caused by the stable backport of "nfsd: fix stale s2s_cp_stateids IDR
> entry for async COPY", which came in with the Ubuntu stable updates.
> This is the fix that went into upstream stable as 7.2.12 (8e42aeb5b39f)
> and 6.18.58 (22732b0f290a), reviewed by Jeff Layton. It applies cleanly
> on top of the current patch queue.
> 
> [...]

Applied, thanks!

[1/1] fix #8121: cherry-pick fix for hanging NFSv4.2 server-side copy
      commit: cbb54eb02d21de2d1d2777e1084161dc92fb38db




      reply	other threads:[~2026-11-06 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  0:48 [PATCH kernel] fix #8121: cherry-pick fix for hanging NFSv4.2 server-side copy Lubos Rendek
2026-11-06 19:32 ` Thomas Lamprecht [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=179399355960.121441.18292885359979936185.b4-ty@b4 \
    --to=t.lamprecht@proxmox.com \
    --cc=l.rendek@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal