All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Cc: "Chuck Lever" <cel@kernel.org>,
	linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	"Lubos Rendek" <l.rendek@proxmox.com>,
	regressions@lists.linux.dev,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [REGRESSION] 7.2.4: nfsd sends CB_OFFLOAD with all-zero stateid, async NFSv4.2 COPY never completes
Date: Tue, 13 Oct 2026 06:15:46 -0400	[thread overview]
Message-ID: <e67eb43ccee21fc4271269e56be668b3dbf1b055.camel@kernel.org> (raw)
In-Reply-To: <2026-10-12-1-daily-reply-0001-nfsd-cb-offload-zero-stateid@kernel.org>

On Mon, 2026-10-12 at 10:59 -0400, Sasha Levin wrote:
> > AFAICT (for 7.2.x) you queued a full pick of
> > 
> > f307b4f7ed17 nfsd: split nfsd4_copy into transient and durable async copy objects
> > 
> > in
> > 
> > 0b2963340727 nfsd: split nfsd4_copy into transient and durable async copy objects
> > 
> > despite Jeff stating the following up-thread:
> > 
> > > We should probably just take Lubos' two-line fix as a separate one-off
> > > patch for stable. Backporting the COPY code refactor is too risky IMO.
> > 
> > Was this intentional, or an accident?
> 
> That was not what Jeff recommended, thanks for catching it. The full pick is
> now dropped from the 7.2 and 6.18 queues.
> 
> Jeff, Chuck: could one of you send that fix as a proper signed-off patch for
> 7.2.y and 6.18.y?

Lubis, since you did the original patch, would you like to send ones
for those releases? Then Chuck and I can just send R-b's for it. If
not, then I'll plan to send some.

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-10-13 10:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 19:30 [REGRESSION] 7.2.4: nfsd sends CB_OFFLOAD with all-zero stateid, async NFSv4.2 COPY never completes Lubos Rendek
2026-10-11  7:19 ` Greg KH
2026-10-11 12:07   ` Jeff Layton
2026-10-11 20:33   ` Lubos Rendek
2026-10-11 16:48 ` Sasha Levin
2026-10-12  9:36   ` Fabian Grünbichler
2026-10-12 14:59     ` Sasha Levin
2026-10-13 10:15       ` Jeff Layton [this message]
2026-10-13 19:45         ` Lubos Rendek

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=e67eb43ccee21fc4271269e56be668b3dbf1b055.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=f.gruenbichler@proxmox.com \
    --cc=l.rendek@proxmox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.