From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@kernel.org>, "Chuck Lever" <cel@kernel.org>,
"Jeff Layton" <jlayton@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: Mon, 12 Oct 2026 10:59:17 -0400 [thread overview]
Message-ID: <2026-10-12-1-daily-reply-0001-nfsd-cb-offload-zero-stateid@kernel.org> (raw)
In-Reply-To: <1791797151.oll70jtyaa.astroid@yuna.none>
> 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?
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-12 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 19:30 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 [this message]
2026-10-13 10:15 ` Jeff Layton
2026-10-13 19:45 ` Lubos Rendek
2026-10-15 0:53 ` [PATCH 7.2.y] nfsd: fix all-zero stateid in CB_OFFLOAD for async COPY Lubos Rendek
2026-10-15 17:14 ` Jeff Layton
2026-10-15 19:35 ` Sasha Levin
2026-10-15 0:57 ` [PATCH 6.18.y] " Lubos Rendek
2026-10-15 17:15 ` Jeff Layton
2026-10-15 19:35 ` Sasha Levin
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=2026-10-12-1-daily-reply-0001-nfsd-cb-offload-zero-stateid@kernel.org \
--to=sashal@kernel.org \
--cc=cel@kernel.org \
--cc=f.gruenbichler@proxmox.com \
--cc=jlayton@kernel.org \
--cc=l.rendek@proxmox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®