mirror of
https://github.com/torvalds/linux.git
synced 2026-07-27 09:36:22 +02:00
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: d343fce148 ("[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>
This commit is contained in:
parent
58202c29de
commit
5cca6056f2
|
|
@ -49,7 +49,7 @@ static inline __be32 cast_status(__be32 status)
|
|||
status = nlm_lck_denied_nolocks;
|
||||
break;
|
||||
default:
|
||||
if (be32_to_cpu(status) >= 30000)
|
||||
if (be32_to_cpu(status) > be32_to_cpu(nlm__int__drop_reply))
|
||||
pr_warn_once("lockd: unhandled internal status %u\n",
|
||||
be32_to_cpu(status));
|
||||
break;
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user