netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alexander Ovechkin <ovov@yandex-team.ru>, netdev@vger.kernel.org
Cc: zeil@yandex-team.ru, dmtrmonakhov@yandex-team.ru
Subject: Re: [PATCH] tcp: relookup sock for RST+ACK packets handled by obsolete req sock
Date: Mon, 15 Mar 2021 11:33:43 +0100	[thread overview]
Message-ID: <7c6d50ad-e09e-fb86-3ee4-c84b76d63417@gmail.com> (raw)
In-Reply-To: <20210311230756.971993-1-ovov@yandex-team.ru>



On 3/12/21 12:07 AM, Alexander Ovechkin wrote:
> Currently tcp_check_req can be called with obsolete req socket for which big
> socket have been already created (because of CPU race or early demux
> assigning req socket to multiple packets in gro batch).
> 
> Commit e0f9759f530bf789e984 (\"tcp: try to keep packet if SYN_RCV race
> is lost\") added retry in case when tcp_check_req is called for PSH|ACK packet.
> But if client sends RST+ACK immediatly after connection being
> established (it is performing healthcheck, for example) retry does not
> occur. In that case tcp_check_req tries to close req socket,
> leaving big socket active.
> 

Please insert the following tag, right before your SOB
Fixes: e0f9759f530 ("tcp: try to keep packet if SYN_RCV race is lost")
> Signed-off-by: Alexander Ovechkin <ovov@yandex-team.ru>
> Reported-by: Oleg Senin <olegsenin@yandex-team.ru>

Please CC TCP maintainer for your TCP patches, I almost missed it.


> ---
>  include/net/inet_connection_sock.h | 2 +-
>  net/ipv4/inet_connection_sock.c    | 6 ++++--
>  net/ipv4/tcp_minisocks.c           | 6 ++++--
>  3 files changed, 9 insertions(+), 5 deletions(-)
> 
> diff --git a/include/net/inet_connection_sock.h b/include/net/inet_connection_sock.h
> index 10a625760de9..3c8c59471bc1 100644
> --- a/include/net/inet_connection_sock.h
> +++ b/include/net/inet_connection_sock.h
> @@ -282,7 +282,7 @@ static inline int inet_csk_reqsk_queue_is_full(const struct sock *sk)
>  	return inet_csk_reqsk_queue_len(sk) >= sk->sk_max_ack_backlog;
>  }
>  
> -void inet_csk_reqsk_queue_drop(struct sock *sk, struct request_sock *req);
> +bool inet_csk_reqsk_queue_drop(struct sock *sk, struct request_sock *req);
>  void inet_csk_reqsk_queue_drop_and_put(struct sock *sk, struct request_sock *req);
>  
>  static inline void inet_csk_prepare_for_destroy_sock(struct sock *sk)
> diff --git a/net/ipv4/inet_connection_sock.c b/net/ipv4/inet_connection_sock.c
> index 6bd7ca09af03..08ca9de2a708 100644
> --- a/net/ipv4/inet_connection_sock.c
> +++ b/net/ipv4/inet_connection_sock.c
> @@ -705,12 +705,14 @@ static bool reqsk_queue_unlink(struct request_sock *req)
>  	return found;
>  }
>  
> -void inet_csk_reqsk_queue_drop(struct sock *sk, struct request_sock *req)
> +bool inet_csk_reqsk_queue_drop(struct sock *sk, struct request_sock *req)
>  {
> -	if (reqsk_queue_unlink(req)) {
> +	bool unlinked = reqsk_queue_unlink(req);

Add an empty line.

> +	if (unlinked) {
>  		reqsk_queue_removed(&inet_csk(sk)->icsk_accept_queue, req);
>  		reqsk_put(req);
>  	}
> +	return unlinked;
>  }
>  EXPORT_SYMBOL(inet_csk_reqsk_queue_drop);
>  
> diff --git a/net/ipv4/tcp_minisocks.c b/net/ipv4/tcp_minisocks.c
> index 0055ae0a3bf8..31ed3423503d 100644
> --- a/net/ipv4/tcp_minisocks.c
> +++ b/net/ipv4/tcp_minisocks.c
> @@ -804,8 +804,10 @@ struct sock *tcp_check_req(struct sock *sk, struct sk_buff *skb,
>  		tcp_reset(sk, skb);
>  	}
>  	if (!fastopen) {
> -		inet_csk_reqsk_queue_drop(sk, req);
> -		__NET_INC_STATS(sock_net(sk), LINUX_MIB_EMBRYONICRSTS);
> +		bool unlinked = inet_csk_reqsk_queue_drop(sk, req);

Same here.

> +		if (unlinked)
> +			__NET_INC_STATS(sock_net(sk), LINUX_MIB_EMBRYONICRSTS);
> +		*req_stolen = !unlinked;
>  	}
>  	return NULL;
>  }
> 

Other than that, your patch looks fine to me, thanks.

      reply	other threads:[~2021-03-15 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 23:07 [PATCH] tcp: relookup sock for RST+ACK packets handled by obsolete req sock Alexander Ovechkin
2021-03-15 10:33 ` Eric Dumazet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7c6d50ad-e09e-fb86-3ee4-c84b76d63417@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=dmtrmonakhov@yandex-team.ru \
    --cc=netdev@vger.kernel.org \
    --cc=ovov@yandex-team.ru \
    --cc=zeil@yandex-team.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).