diff options
| author | Jeff Layton <jlayton@kernel.org> | 2026-09-15 12:57:44 -0400 |
|---|---|---|
| committer | Chuck Lever <cel@kernel.org> | 2026-10-11 23:11:57 -0400 |
| commit | 8fbc15adbbfcf5a3b1b883490c34fd06947058c6 (patch) | |
| tree | fa328455b8404d5e4ac0dd88f16cc4554d19f2ab /rust/kernel/alloc/allocator | |
| parent | 7b5c04bc59209551c4a93cd043df974c28227f4f (diff) | |
NFSD: honour the userspace-rpcbind flag in listener_set
A listener_set request that carries userspace-rpcbind now sets
sv_no_rpcbind on the serv. The kernel then makes no rpcbind call at all,
avoiding synchronous rpcbind RPCs under nfsd_mutex.
Ownership cannot change under a live serv. An empty listener list is
exempt: it destroys the serv, and nfsd_destroy_serv() drops whatever
svc_bind() took either way, so teardown is not an ownership change.
Without the exemption a caller that never learned about the flag could
not shut nfsd down, and the extack blamed an ownership change it had not
asked for. nfsd_nl_validate_listeners() returns the entry count so the
gate can tell the two cases apart.
The legacy portlist add-fd interface refuses to run against such a serv.
nfsd_create_serv() returns early when the serv exists, so it cannot flip
ownership back, svc_addsock() does not pass SVC_SOCK_ANONYMOUS and so
expects svc_register() to register the listener, and there is no way to
tell the rpcbind owner about it. -EBUSY, matching listener_set. add-xprt
already passes SVC_SOCK_ANONYMOUS and never registered anything.
lockd is unaffected. It owns a separate svc_serv and still registers NLM.
Assisted-by: LLM
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Link: https://patch.msgid.link/20260915-nfsd-norpcb-v3-3-3c60d49ade02@kernel.org
Signed-off-by: Chuck Lever <cel@kernel.org>
Diffstat (limited to 'rust/kernel/alloc/allocator')
0 files changed, 0 insertions, 0 deletions
