diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2025-08-20 10:27:27 -0400 |
---|---|---|
committer | Chuck Lever <chuck.lever@oracle.com> | 2025-09-21 19:24:50 -0400 |
commit | dd9adfa0da2b0dac4c0abdae4bdb88c366bd83d5 (patch) | |
tree | e3d7921d4c5b03fd73d046db4c0d2ea2b8d91502 /drivers/infiniband/hw/ionic/ionic_datapath.c | |
parent | 898374fdd7f06fa4c4a66e8be3135efeae6128d5 (diff) |
NFS: Remove rpcbind cleanup for NFSv4.0 callback
The NFS client's NFSv4.0 callback listeners are created with
SVC_SOCK_ANONYMOUS, therefore svc_setup_socket() does not register
them with the client's rpcbind service.
And, note that nfs_callback_down_net() does not call
svc_rpcb_cleanup() at all when shutting down the callback server.
Even if svc_setup_socket() were to attempt to register or unregister
these sockets, the callback service has vs_hidden set, which shunts
the rpcbind upcalls.
The svc_rpcb_cleanup() error flow was introduced by
commit c946556b8749 ("NFS: move per-net callback thread
initialization to nfs_callback_up_net()"). It doesn't appear in the
code that was relocated by that commit.
Therefore, there is no need to call svc_rpcb_cleanup() when listener
creation fails during callback server start-up.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'drivers/infiniband/hw/ionic/ionic_datapath.c')
0 files changed, 0 insertions, 0 deletions