From: patchwork-bot+netdevbpf@kernel.org
To: Francesco Ruggeri <fruggeri@arista.com>
Cc: pabeni@redhat.com, kuba@kernel.org, dsahern@kernel.org,
yoshfuji@linux-ipv6.org, davem@davemloft.net,
edumazet@google.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 net] tcp: md5: incorrect tcp_header_len for incoming connections
Date: Fri, 22 Apr 2022 22:20:12 +0000 [thread overview]
Message-ID: <165066601253.17746.2255249203148338043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220421005026.686A45EC01F2@us226.sjc.aristanetworks.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 Apr 2022 17:50:26 -0700 you wrote:
> In tcp_create_openreq_child we adjust tcp_header_len for md5 using the
> remote address in newsk. But that address is still 0 in newsk at this
> point, and it is only set later by the callers (tcp_v[46]_syn_recv_sock).
> Use the address from the request socket instead.
>
> v2: Added "Fixes:" line.
>
> [...]
Here is the summary with links:
- [v2,net] tcp: md5: incorrect tcp_header_len for incoming connections
https://git.kernel.org/netdev/net/c/5b0b9e4c2c89
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-04-22 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 0:50 [PATCH v2 net] tcp: md5: incorrect tcp_header_len for incoming connections Francesco Ruggeri
2022-04-21 2:00 ` Eric Dumazet
2022-04-22 22:20 ` patchwork-bot+netdevbpf [this message]
2022-04-24 19:36 ` Eric Dumazet
2022-04-25 17:55 ` Francesco Ruggeri
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=165066601253.17746.2255249203148338043.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/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