netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Xing <kerneljasonxing@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, dsahern@kernel.org, kuniyu@amazon.com
Cc: netdev@vger.kernel.org, kerneljasonxing@gmail.com,
	Jason Xing <kernelxing@tencent.com>
Subject: [PATCH net-next v7 02/11] tcp: directly drop skb in cookie check for ipv4
Date: Wed, 21 Feb 2024 10:57:22 +0800	[thread overview]
Message-ID: <20240221025732.68157-3-kerneljasonxing@gmail.com> (raw)
In-Reply-To: <20240221025732.68157-1-kerneljasonxing@gmail.com>

From: Jason Xing <kernelxing@tencent.com>

Only move the skb drop from tcp_v4_do_rcv() to cookie_v4_check() itself,
no other changes made. It can help us refine the specific drop reasons
later.

Signed-off-by: Jason Xing <kernelxing@tencent.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
--
v7
Link: https://lore.kernel.org/all/20240219041350.95304-1-kuniyu@amazon.com/
1. add reviewed-by tag (Kuniyuki)
---
 net/ipv4/syncookies.c | 4 ++++
 net/ipv4/tcp_ipv4.c   | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/net/ipv4/syncookies.c b/net/ipv4/syncookies.c
index be88bf586ff9..38f331da6677 100644
--- a/net/ipv4/syncookies.c
+++ b/net/ipv4/syncookies.c
@@ -408,6 +408,7 @@ struct sock *cookie_v4_check(struct sock *sk, struct sk_buff *skb)
 	struct rtable *rt;
 	__u8 rcv_wscale;
 	int full_space;
+	SKB_DR(reason);
 
 	if (!READ_ONCE(net->ipv4.sysctl_tcp_syncookies) ||
 	    !th->ack || th->rst)
@@ -477,10 +478,13 @@ struct sock *cookie_v4_check(struct sock *sk, struct sk_buff *skb)
 	 */
 	if (ret)
 		inet_sk(ret)->cork.fl.u.ip4 = fl4;
+	else
+		goto out_drop;
 out:
 	return ret;
 out_free:
 	reqsk_free(req);
 out_drop:
+	kfree_skb_reason(skb, reason);
 	return NULL;
 }
diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
index 0c50c5a32b84..0a944e109088 100644
--- a/net/ipv4/tcp_ipv4.c
+++ b/net/ipv4/tcp_ipv4.c
@@ -1915,7 +1915,7 @@ int tcp_v4_do_rcv(struct sock *sk, struct sk_buff *skb)
 		struct sock *nsk = tcp_v4_cookie_check(sk, skb);
 
 		if (!nsk)
-			goto discard;
+			return 0;
 		if (nsk != sk) {
 			if (tcp_child_process(sk, nsk, skb)) {
 				rsk = nsk;
-- 
2.37.3


  parent reply	other threads:[~2024-02-21  2:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  2:57 [PATCH net-next v7 00/11] introduce drop reasons for tcp receive path Jason Xing
2024-02-21  2:57 ` [PATCH net-next v7 01/11] tcp: add a dropreason definitions and prepare for cookie check Jason Xing
2024-02-21  9:35   ` Eric Dumazet
2024-02-21  2:57 ` Jason Xing [this message]
2024-02-21  9:28   ` [PATCH net-next v7 02/11] tcp: directly drop skb in cookie check for ipv4 Eric Dumazet
2024-02-21  2:57 ` [PATCH net-next v7 03/11] tcp: use drop reasons " Jason Xing
2024-02-21  9:34   ` Eric Dumazet
2024-02-22  2:52     ` Jason Xing
2024-02-21  2:57 ` [PATCH net-next v7 04/11] tcp: directly drop skb in cookie check for ipv6 Jason Xing
2024-02-21  9:36   ` Eric Dumazet
2024-02-21  2:57 ` [PATCH net-next v7 05/11] tcp: use drop reasons " Jason Xing
2024-02-21  9:37   ` Eric Dumazet
2024-02-21  2:57 ` [PATCH net-next v7 06/11] tcp: introduce dropreasons in receive path Jason Xing
2024-02-21  2:57 ` [PATCH net-next v7 07/11] tcp: add more specific possible drop reasons in tcp_rcv_synsent_state_process() Jason Xing
2024-02-21  9:59   ` Eric Dumazet
2024-02-21  2:57 ` [PATCH net-next v7 08/11] tcp: add dropreasons in tcp_rcv_state_process() Jason Xing
2024-02-21 10:12   ` Eric Dumazet
2024-02-21  2:57 ` [PATCH net-next v7 09/11] tcp: make the dropreason really work when calling tcp_rcv_state_process() Jason Xing
2024-02-21 14:42   ` Eric Dumazet
2024-02-21  2:57 ` [PATCH net-next v7 10/11] tcp: make dropreason in tcp_child_process() work Jason Xing
2024-02-21 14:44   ` Eric Dumazet
2024-02-22  2:25     ` Jason Xing
2024-02-21  2:57 ` [PATCH net-next v7 11/11] tcp: get rid of NOT_SPECIFIED reason in tcp_v4/6_do_rcv Jason Xing
2024-02-21 14:47   ` Eric Dumazet
2024-02-22  2:16     ` Jason Xing

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=20240221025732.68157-3-kerneljasonxing@gmail.com \
    --to=kerneljasonxing@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kernelxing@tencent.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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).