From: Tj <tj.iam.tj@proton.me>
To: 1128861@bugs.debian.org, Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org,
Olga Kornievskaia <okorniev@redhat.com>,
stable@vger.kernel.org
Subject: Re: Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available
Date: Tue, 24 Feb 2026 12:50:22 +0000 [thread overview]
Message-ID: <7945477d-f6f9-4311-9ef3-73a92f0e8ea2@proton.me> (raw)
In-Reply-To: <c0f15088-3fc0-487a-9f24-cf89c158420d@proton.me>
Follow-up with results of adding dump_stack() to nfsd_permission()
revealing the paths that trigger the issue.
[ 133.185579] Call Trace:
[ 133.185580] <TASK>
[ 133.185580] dump_stack_lvl+0x64/0x80
[ 133.185582] nfsd_permission+0x20/0x100 [nfsd]
[ 133.185612] nfsd_access+0xc8/0x140 [nfsd]
[ 133.185639] nfsd4_proc_compound+0x350/0x670 [nfsd]
[ 133.185670] nfsd_dispatch+0x100/0x220 [nfsd]
[ 133.185698] svc_process_common+0x314/0x700 [sunrpc]
[ 133.185733] ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd]
[ 133.185762] svc_process+0x131/0x1c0 [sunrpc]
[ 133.185795] svc_recv+0x80a/0x9e0 [sunrpc]
[ 133.185827] ? __pfx_nfsd+0x10/0x10 [nfsd]
[ 133.185856] nfsd+0xa3/0x100 [nfsd]
[ 133.185882] kthread+0xd2/0x100
[ 133.185884] ? __pfx_kthread+0x10/0x10
[ 133.185885] ret_from_fork+0x34/0x50
[ 133.185886] ? __pfx_kthread+0x10/0x10
[ 133.185887] ret_from_fork_asm+0x1a/0x30
[ 133.185890] </TASK>
[ 144.020165] Call Trace:
[ 144.020165] <TASK>
[ 144.020166] dump_stack_lvl+0x64/0x80
[ 144.020168] nfsd_permission+0x20/0x100 [nfsd]
[ 144.020201] nfsd_access+0xc8/0x140 [nfsd]
[ 144.020228] nfsd3_proc_access+0x6c/0x110 [nfsd]
[ 144.020257] nfsd_dispatch+0x100/0x220 [nfsd]
[ 144.020286] svc_process_common+0x314/0x700 [sunrpc]
[ 144.020321] ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd]
[ 144.020350] svc_process+0x131/0x1c0 [sunrpc]
[ 144.020383] svc_recv+0x80a/0x9e0 [sunrpc]
[ 144.020415] ? __pfx_nfsd+0x10/0x10 [nfsd]
[ 144.020445] nfsd+0xa3/0x100 [nfsd]
[ 144.020471] kthread+0xd2/0x100
[ 144.020472] ? __pfx_kthread+0x10/0x10
[ 144.020473] ret_from_fork+0x34/0x50
[ 144.020475] ? __pfx_kthread+0x10/0x10
[ 144.020476] ret_from_fork_asm+0x1a/0x30
[ 144.020478] </TASK>
next prev parent reply other threads:[~2026-02-24 12:50 UTC|newest]
Thread overview: 19+ 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 [this message]
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-25 20:29 ` Bug#1128861: " 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=7945477d-f6f9-4311-9ef3-73a92f0e8ea2@proton.me \
--to=tj.iam.tj@proton.me \
--cc=1128861@bugs.debian.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--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