rxrpc: Fix received abort handling

Web:        https://git.kernel.org/torvalds/c/17e9e23b130e4e269fa53c2370325249f3ba75dd
Commit:     17e9e23b130e4e269fa53c2370325249f3ba75dd
Parent:     e729452ec33304260d4741e9ce67784a457ee1e6
Refname:    refs/heads/master
Author:     David Howells <[email protected]>
AuthorDate: Tue Feb 6 16:44:12 2018 +0000
Committer:  David S. Miller <[email protected]>
CommitDate: Wed Feb 7 21:47:10 2018 -0500

    rxrpc: Fix received abort handling
    
    AF_RXRPC is incorrectly sending back to the server any abort it receives
    for a client connection.  This is due to the final-ACK offload to the
    connection event processor patch.  The abort code is copied into the
    last-call information on the connection channel and then the event
    processor is set.
    
    Instead, the following should be done:
    
     (1) In the case of a final-ACK for a successful call, the ACK should be
         scheduled as before.
    
     (2) In the case of a locally generated ABORT, the ABORT details should be
         cached for sending in response to further packets related to that
         call and no further action scheduled at call disconnect time.
    
     (3) In the case of an ACK received from the peer, the call should be
         considered dead, no ABORT should be transmitted at this time.  In
         response to further non-ABORT packets from the peer relating to this
         call, an RX_USER_ABORT ABORT should be transmitted.
    
     (4) In the case of a call killed due to network error, an RX_USER_ABORT
         ABORT should be cached for transmission in response to further
         packets, but no ABORT should be sent at this time.
    
    Fixes: 3136ef49a14c ("rxrpc: Delay terminal ACK transmission on a client call")
    Signed-off-by: David Howells <[email protected]>
    Signed-off-by: David S. Miller <[email protected]>
---
 net/rxrpc/conn_client.c |  3 ++-
 net/rxrpc/conn_object.c | 16 ++++++++++++----
 2 files changed, 14 insertions(+), 5 deletions(-)

diff --git a/net/rxrpc/conn_client.c b/net/rxrpc/conn_client.c
index 7f74ca3059f8..064175068059 100644
--- a/net/rxrpc/conn_client.c
+++ b/net/rxrpc/conn_client.c
@@ -834,7 +834,8 @@ void rxrpc_disconnect_client_call(struct rxrpc_call *call)
 	 * can be skipped if we find a follow-on call.  The first DATA packet
 	 * of the follow on call will implicitly ACK this call.
 	 */
-	if (test_bit(RXRPC_CALL_EXPOSED, &call->flags)) {
+	if (call->completion == RXRPC_CALL_SUCCEEDED &&
+	    test_bit(RXRPC_CALL_EXPOSED, &call->flags)) {
 		unsigned long final_ack_at = jiffies + 2;
 
 		WRITE_ONCE(chan->final_ack_at, final_ack_at);
diff --git a/net/rxrpc/conn_object.c b/net/rxrpc/conn_object.c
index c628351eb900..ccbac190add1 100644
--- a/net/rxrpc/conn_object.c
+++ b/net/rxrpc/conn_object.c
@@ -177,13 +177,21 @@ void __rxrpc_disconnect_call(struct rxrpc_connection *conn,
 		 * through the channel, whilst disposing of the actual call record.
 		 */
 		trace_rxrpc_disconnect_call(call);
-		if (call->abort_code) {
-			chan->last_abort = call->abort_code;
-			chan->last_type = RXRPC_PACKET_TYPE_ABORT;
-		} else {
+		switch (call->completion) {
+		case RXRPC_CALL_SUCCEEDED:
 			chan->last_seq = call->rx_hard_ack;
 			chan->last_type = RXRPC_PACKET_TYPE_ACK;
+			break;
+		case RXRPC_CALL_LOCALLY_ABORTED:
+			chan->last_abort = call->abort_code;
+			chan->last_type = RXRPC_PACKET_TYPE_ABORT;
+			break;
+		default:
+			chan->last_abort = RX_USER_ABORT;
+			chan->last_type = RXRPC_PACKET_TYPE_ABORT;
+			break;
 		}
+
 		/* Sync with rxrpc_conn_retransmit(). */
 		smp_wmb();
 		chan->last_call = chan->call_id;
--
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html