afs: Differentiate abort due to unmarshalling from other errors

Differentiate an abort due to an unmarshalling error from an abort due to
other errors, such as ENETUNREACH.  It doesn't make sense to set abort code
RXGEN_*_UNMARSHAL in such a case, so use RX_USER_ABORT instead.

Signed-off-by: David Howells <dhowells@redhat.com>

1 files changed, 5 insertions, 1 deletions

diff --git a/fs/afs/rxrpc.c b/fs/afs/rxrpc.c
index c14001b42d20..15c7e82d80cb 100644
--- a/fs/afs/rxrpc.c
+++ b/fs/afs/rxrpc.c
@@ -572,13 +572,17 @@ static void afs_deliver_to_call(struct afs_call *call)
                 case -ENODATA:
                 case -EBADMSG:
                 case -EMSGSIZE:
-                default:
                         abort_code = RXGEN_CC_UNMARSHAL;
                         if (state != AFS_CALL_CL_AWAIT_REPLY)
                                 abort_code = RXGEN_SS_UNMARSHAL;
                         rxrpc_kernel_abort_call(call->net->socket, call->rxcall,
                                                 abort_code, ret, "KUM");
                         goto local_abort;
+                default:
+                        abort_code = RX_USER_ABORT;
+                        rxrpc_kernel_abort_call(call->net->socket, call->rxcall,
+                                                abort_code, ret, "KER");
+                        goto local_abort;
                 }
         }