From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Tj <tj.iam.tj@proton.me>,
1128861@bugs.debian.org, Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org,
Olga Kornievskaia <okorniev@redhat.com>,
stable@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available
Date: Fri, 27 Feb 2026 10:54:13 +0100 [thread overview]
Message-ID: <418f30b5-06ae-471f-bf5f-f14f3f75deff@leemhuis.info> (raw)
In-Reply-To: <c0f15088-3fc0-487a-9f24-cf89c158420d@proton.me>
[CCing a few people and lists]
On 2/24/26 03:09, Tj wrote:
> Upstream commit 4cc9b9f2bf4dfe13fe573 "nfsd: refine and rename
> NFSD_MAY_LOCK" and
> stable v6.12.54 commit 18744bc56b0ec
In case anyone just like me is wondering: the latter is a backport of
the former.
> (re)moves checks from fs/nfsd/vfs.c::nfsd_permission().> This causes NFS clients to see
>
> $ flock -e -w 4 /srv/NAS/test/debian-13.3.0-amd64-netinst.iso sleep 1
> flock: /srv/NAS/test/debian-13.3.0-amd64-netinst.iso: No locks available
Does this happen on mainline (e.g. 7.0-rc1) as well?
Ciao, Thorsten
> Keeping the check in nfsd_permission() whilst also copying it to
> fs/nfsd/nfsfh.c::__fh_verify() resolves the issue.
>
> This was discovered on the Debian openQA infrastructure server when
> upgrading kernel from v6.12.48 to later v6.12.y where worker hosts (with
> any earlier or later kernel version) pass NFSv3 mounted ISO images to
> qemu-system-x86_64 and it reports:
>
> !!! : qemu-system-x86_64: -device
> scsi-cd,id=cd0-device,drive=cd0-overlay0,serial=cd0: Failed to get
> "consistent read" lock: No locks available
> QEMU: Is another process using the image
> [/var/lib/openqa/pool/2/20260223-1-debian-testing-amd64-netinst.iso]?
>
> A simple reproducer with the server using:
>
> # cat /etc/exports.d/test.exports
> /srv/NAS/test
> fdff::/64(fsid=0,rw,no_root_squash,sync,no_subtree_check,auth_nlm)
>
> and clients using:
>
> # mount -t nfs [fdff::2]:/srv/NAS/test /srv/NAS/test -o
> proto=tcp6,ro,fsc,soft
>
> will trigger the error as shown above:
>
> $ flock -e -w 4 /srv/NAS/test/debian-13.3.0-amd64-netinst.iso sleep 1
> flock: /srv/NAS/test/debian-13.3.0-amd64-netinst.iso: No locks available
>
> A simple test program calling fcntl() with the same arguments QEMU uses
> also fails in the same way.
>
> $ ./nfs3_range_lock_test
> /srv/NAS/test/debian-13.3.0-amd64-netinst.{iso,overlay}
> Opened base file: /srv/NAS/test/debian-13.3.0-amd64-netinst.iso
> Opened overlay file: /srv/NAS/test/debian-13.3.0-amd64-netinst.overlay
> Attempting lock at 4 on /srv/NAS/test/debian-13.3.0-amd64-netinst.iso
> fcntl(fd, F_GETLK, &fl) failed on base: No locks available
> Attempting lock at 8 on /srv/NAS/test/debian-13.3.0-amd64-netinst.overlay
> fcntl(fd, F_GETLK, &fl) failed on overlay: No locks available
>
>
next prev parent reply other threads:[~2026-02-27 9:54 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 [this message]
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 ` Bug#1128861: " Uwe Kleine-König
2026-04-01 13:34 ` 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=418f30b5-06ae-471f-bf5f-f14f3f75deff@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=1128861@bugs.debian.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).