From: "Uwe Kleine-König" <ukleinek@debian.org>
To: Chuck Lever <cel@kernel.org>, 1128861@bugs.debian.org
Cc: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Tj <tj.iam.tj@proton.me>,
linux-nfs@vger.kernel.org,
Olga Kornievskaia <okorniev@redhat.com>,
stable@vger.kernel.org
Subject: Re: Bug#1128861: [PATCH v2] lockd: fix TEST handling when not all permissions are available.
Date: Wed, 1 Apr 2026 14:54:18 +0200 [thread overview]
Message-ID: <ac0U4P92l-TkQvnh@monoceros> (raw)
In-Reply-To: <465012d6-c824-4d8d-b6f6-8a2d85e30154@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
Hello Chuck,
On Fri, Mar 27, 2026 at 09:56:38AM -0400, Chuck Lever wrote:
> I think the stable folks will insist on this fix going into
> upstream first. However, this version of the fix does not
> apply to nfsd-testing because that branch has the NLMv4
> xdrgen rewrite.
This is not the first time a bug is fixed by changes that are too
intrusive for backport. Usually the stable maintainers can be talked to
accept a small targeted fix even if it's not upstream. The discussion is
simplified by people claiming to have tested the fix and confirm it
helps.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-01 13:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 2:09 Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available Tj
2026-02-24 12:50 ` Tj
2026-02-27 9:54 ` Thorsten Leemhuis
2026-03-04 10:28 ` Bug#1128861: " Salvatore Bonaccorso
2026-03-04 15:05 ` Olga Kornievskaia
2026-03-12 12:30 ` Jeff Layton
2026-03-12 22:39 ` NeilBrown
2026-03-13 14:11 ` Jeff Layton
2026-03-04 15:44 ` Sasha Levin
2026-03-04 23:03 ` NeilBrown
2026-03-12 8:55 ` Thorsten Leemhuis
2026-03-12 12:10 ` Jeff Layton
2026-03-24 10:13 ` [PATCH] lockd: fix TEST handling when not all permissions are available NeilBrown
2026-03-24 11:25 ` Jeff Layton
2026-03-25 6:44 ` NeilBrown
2026-03-24 14:59 ` Chuck Lever
2026-03-25 7:08 ` NeilBrown
2026-03-25 13:28 ` Chuck Lever
2026-03-26 22:33 ` NeilBrown
2026-03-26 22:47 ` [PATCH v2] " NeilBrown
2026-03-27 13:56 ` Chuck Lever
2026-04-01 12:54 ` Uwe Kleine-König [this message]
2026-04-01 13:34 ` Bug#1128861: " Chuck Lever
2026-03-25 20:29 ` Bug#1128861: [PATCH] " Ben Hutchings
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=ac0U4P92l-TkQvnh@monoceros \
--to=ukleinek@debian.org \
--cc=1128861@bugs.debian.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=regressions@leemhuis.info \
--cc=stable@vger.kernel.org \
--cc=tj.iam.tj@proton.me \
/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