On Thu, Jan 30, 2025 at 9:09 AM Chuck Lever via Bugspray Bot <bugbot@xxxxxxxxxx> wrote: > > Chuck Lever writes via Kernel.org Bugzilla: > > I recommended a separate bug because this looks to me like the CB_GETATTR reply handling path needs some attention. I'm not sure the problems here will result in the hanging symptoms seen in Bug #218735. > > First issue is the explicit use of NFS4ERR_BAD_XDR in the CB_GETATTR reply decoder. Should be EIO instead. > > Second issue is the CB_GETATTR reply decoder does not seem capable of handling a non-zero status code in the reply. > > Third issue is whether NFS4ERR_BADHANDLE means the server requested a CB_GETATTR for the wrong file, or if it is an expected situation. Isn't this because 6.12.x is still missing the patch "NFSD: fix decoding in nfs4_xdr_dec_cb_getattr" that just went into 6.14? > View: https://bugzilla.kernel.org/show_bug.cgi?id=219737#c1 > You can reply to this message to join the discussion. > -- > Deet-doot-dot, I am a bot. > Kernel.org Bugzilla (bugspray 0.1-dev) > >
