From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
martin.lau@kernel.org, kuniyu@amazon.com, ncardwell@google.com,
brianvv@google.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH v3 net-next 0/5] tcp: add skb->sk to more control packets
Date: Tue, 15 Oct 2024 01:00:32 +0000 [thread overview]
Message-ID: <172895403276.684316.13099111913312204295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241010174817.1543642-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Oct 2024 17:48:12 +0000 you wrote:
> Currently, TCP can set skb->sk for a variety of transmit packets.
>
> However, packets sent on behalf of a TIME_WAIT sockets do not
> have an attached socket.
>
> Same issue for RST packets.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/5] net: add TIME_WAIT logic to sk_to_full_sk()
https://git.kernel.org/netdev/net-next/c/78e2baf3d96e
- [v3,net-next,2/5] net_sched: sch_fq: prepare for TIME_WAIT sockets
https://git.kernel.org/netdev/net-next/c/bc43a3c83cad
- [v3,net-next,3/5] net: add skb_set_owner_edemux() helper
https://git.kernel.org/netdev/net-next/c/5ced52fa8f0d
- [v3,net-next,4/5] ipv6: tcp: give socket pointer to control skbs
https://git.kernel.org/netdev/net-next/c/507a96737d99
- [v3,net-next,5/5] ipv4: tcp: give socket pointer to control skbs
https://git.kernel.org/netdev/net-next/c/79636038d37e
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-10-15 1:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 17:48 [PATCH v3 net-next 0/5] tcp: add skb->sk to more control packets Eric Dumazet
2024-10-10 17:48 ` [PATCH v3 net-next 1/5] net: add TIME_WAIT logic to sk_to_full_sk() Eric Dumazet
2024-10-11 23:20 ` Kuniyuki Iwashima
2024-10-12 3:32 ` Martin KaFai Lau
2024-10-14 14:01 ` Brian Vazquez
2024-10-14 14:27 ` Eric Dumazet
2024-10-14 15:08 ` Brian Vazquez
[not found] ` <CAMzD94TytK5RfDvLKXfxR7nys=voptywE3_3zSFymXNCky0AsQ@mail.gmail.com>
2024-10-14 15:23 ` Eric Dumazet
2024-10-14 15:39 ` Brian Vazquez
2024-10-10 17:48 ` [PATCH v3 net-next 2/5] net_sched: sch_fq: prepare for TIME_WAIT sockets Eric Dumazet
2024-10-11 23:25 ` Kuniyuki Iwashima
2024-10-14 14:05 ` Brian Vazquez
2024-10-10 17:48 ` [PATCH v3 net-next 3/5] net: add skb_set_owner_edemux() helper Eric Dumazet
2024-10-11 23:29 ` Kuniyuki Iwashima
2024-10-14 14:20 ` Brian Vazquez
2024-10-14 14:23 ` Eric Dumazet
2024-10-14 14:34 ` Brian Vazquez
2024-10-10 17:48 ` [PATCH v3 net-next 4/5] ipv6: tcp: give socket pointer to control skbs Eric Dumazet
2024-10-11 23:32 ` Kuniyuki Iwashima
2024-10-14 14:22 ` Brian Vazquez
2024-10-10 17:48 ` [PATCH v3 net-next 5/5] ipv4: " Eric Dumazet
2024-10-11 23:41 ` Kuniyuki Iwashima
2024-10-14 14:23 ` Brian Vazquez
2024-10-15 1:00 ` 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=172895403276.684316.13099111913312204295.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=martin.lau@kernel.org \
--cc=ncardwell@google.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).