nfsd: safer handling of corrupted c_type
[ Upstream commit c25bf185e5
]
This can only happen if there's a bug somewhere, so let's make it a WARN
not a printk. Also, I think it's safest to ignore the corruption rather
than trying to fix it by removing a cache entry.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
5.4-rM2-2.2.x-imx-squashed
parent
e585a8b540
commit
ca0cac3373
|
@ -469,8 +469,7 @@ found_entry:
|
||||||
rtn = RC_REPLY;
|
rtn = RC_REPLY;
|
||||||
break;
|
break;
|
||||||
default:
|
default:
|
||||||
printk(KERN_WARNING "nfsd: bad repcache type %d\n", rp->c_type);
|
WARN_ONCE(1, "nfsd: bad repcache type %d\n", rp->c_type);
|
||||||
nfsd_reply_cache_free_locked(b, rp, nn);
|
|
||||||
}
|
}
|
||||||
|
|
||||||
goto out;
|
goto out;
|
||||||
|
|
Loading…
Reference in New Issue