This short series addresses two separate issues related with NFSv4.1 client initialization. The first is an issue with backchannel parameter verification when negotiating with a non-linux nfs server that does not accept larger max_resp_sz values. The second issue is a side-effect of the first (although it could be caused by number of other failures during CREATE_SESSION), which makes mount hang due to lack of -EINVAL error handling in the nfs4_state_manager. Anthony Iliopoulos (2): NFSv4.1: fix backchannel max_resp_sz verification check NFSv4.1: fix mount hang after CREATE_SESSION failure fs/nfs/nfs4proc.c | 2 +- fs/nfs/nfs4state.c | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) -- 2.50.1
