The smc code never checks the sk_write_pending sock field.
Thus there is no need to update it.

Signed-off-by: Ursula Braun <ubr...@linux.vnet.ibm.com>
---
 net/smc/smc_tx.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/net/smc/smc_tx.c b/net/smc/smc_tx.c
index c48dc2d5fd3a..77555c6ed199 100644
--- a/net/smc/smc_tx.c
+++ b/net/smc/smc_tx.c
@@ -104,14 +104,12 @@ static int smc_tx_wait_memory(struct smc_sock *smc, int 
flags)
                if (atomic_read(&conn->sndbuf_space))
                        break; /* at least 1 byte of free space available */
                set_bit(SOCK_NOSPACE, &sk->sk_socket->flags);
-               sk->sk_write_pending++;
                sk_wait_event(sk, &timeo,
                              sk->sk_err ||
                              (sk->sk_shutdown & SEND_SHUTDOWN) ||
                              smc_cdc_rxed_any_close_or_senddone(conn) ||
                              atomic_read(&conn->sndbuf_space),
                              &wait);
-               sk->sk_write_pending--;
        }
        remove_wait_queue(sk_sleep(sk), &wait);
        return rc;
-- 
2.13.5

Reply via email to