From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, kuniyu@amazon.com,
netdev@vger.kernel.org, kernelxing@tencent.com
Subject: Re: [PATCH net-next v10 00/10] introduce drop reasons for tcp receive path
Date: Wed, 28 Feb 2024 10:50:33 +0000 [thread overview]
Message-ID: <170911743374.15474.6211464866179715497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240226032227.15255-1-kerneljasonxing@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 26 Feb 2024 11:22:17 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> When I was debugging the reason about why the skb should be dropped in
> syn cookie mode, I found out that this NOT_SPECIFIED reason is too
> general. Thus I decided to refine it.
>
> v10
> Link: https://lore.kernel.org/netdev/20240223193321.6549-1-kuniyu@amazon.com/
> 1. fix three nit problems (Kuniyuki)
> 2. add reviewed-by tag (Kuniyuki)
>
> [...]
Here is the summary with links:
- [net-next,v10,01/10] tcp: add a dropreason definitions and prepare for cookie check
https://git.kernel.org/netdev/net-next/c/48e4704aedb9
- [net-next,v10,02/10] tcp: directly drop skb in cookie check for ipv4
https://git.kernel.org/netdev/net-next/c/65be4393f363
- [net-next,v10,03/10] tcp: use drop reasons in cookie check for ipv4
https://git.kernel.org/netdev/net-next/c/a4a69a3719ec
- [net-next,v10,04/10] tcp: directly drop skb in cookie check for ipv6
https://git.kernel.org/netdev/net-next/c/ed43e76cdcc4
- [net-next,v10,05/10] tcp: use drop reasons in cookie check for ipv6
https://git.kernel.org/netdev/net-next/c/253541a3c1e4
- [net-next,v10,06/10] tcp: introduce dropreasons in receive path
https://git.kernel.org/netdev/net-next/c/3d359faba191
- [net-next,v10,07/10] tcp: add more specific possible drop reasons in tcp_rcv_synsent_state_process()
https://git.kernel.org/netdev/net-next/c/e615e3a24ed6
- [net-next,v10,08/10] tcp: add dropreasons in tcp_rcv_state_process()
https://git.kernel.org/netdev/net-next/c/7d6ed9afde85
- [net-next,v10,09/10] tcp: make the dropreason really work when calling tcp_rcv_state_process()
https://git.kernel.org/netdev/net-next/c/b98256959305
- [net-next,v10,10/10] tcp: make dropreason in tcp_child_process() work
https://git.kernel.org/netdev/net-next/c/ee01defe25ba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-02-28 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 3:22 [PATCH net-next v10 00/10] introduce drop reasons for tcp receive path Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 01/10] tcp: add a dropreason definitions and prepare for cookie check Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 02/10] tcp: directly drop skb in cookie check for ipv4 Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 03/10] tcp: use drop reasons " Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 04/10] tcp: directly drop skb in cookie check for ipv6 Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 05/10] tcp: use drop reasons " Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 06/10] tcp: introduce dropreasons in receive path Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 07/10] tcp: add more specific possible drop reasons in tcp_rcv_synsent_state_process() Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 08/10] tcp: add dropreasons in tcp_rcv_state_process() Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 09/10] tcp: make the dropreason really work when calling tcp_rcv_state_process() Jason Xing
2024-02-26 3:22 ` [PATCH net-next v10 10/10] tcp: make dropreason in tcp_child_process() work Jason Xing
2024-02-28 10:50 ` patchwork-bot+netdevbpf [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=170911743374.15474.6211464866179715497.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.