diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2026-05-12 21:13:36 +0300 |
|---|---|---|
| committer | Chuck Lever <cel@kernel.org> | 2026-06-09 23:32:59 +0300 |
| commit | 5cca6056f2bae9be14566e0f7f6e351103a6aef3 (patch) | |
| tree | d193a14f7775313fe3a2c9c5a2d0d9fb264b1d01 /include/linux/node.h | |
| parent | 58202c29de9360a2b255458892e08a252d4406be (diff) | |
| download | linux-5cca6056f2bae9be14566e0f7f6e351103a6aef3.tar.xz | |
lockd: Stop warning on nlm__int__drop_reply in !V4 cast_status
cast_status folds internal lock-daemon sentinels into NLMv1/v3
wire status codes. The !CONFIG_LOCKD_V4 variant warns when an
unrecognized status falls into the internal-sentinel range,
gated by be32_to_cpu(status) >= 30000.
nlm__int__drop_reply is defined as cpu_to_be32(30000), so it
sits at the lower edge of that range and trips pr_warn_once
("lockd: unhandled internal status %u"). The status is
returned unchanged so the reply is still dropped, but every
dropped reply on a !CONFIG_LOCKD_V4 build emits a spurious
warning.
Compare against nlm__int__drop_reply directly so the warning
still catches the genuinely unexpected sentinels deadlock,
stale_fh, and failed (30001 through 30003) but excludes the
legitimate dropped-reply marker.
Fixes: d343fce148a4 ("[PATCH] knfsd: Allow lockd to drop replies as appropriate")
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'include/linux/node.h')
0 files changed, 0 insertions, 0 deletions
