From: patchwork-bot+netdevbpf@kernel•org
To: Jakub Kicinski <kuba@kernel•org>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
pabeni@redhat•com, yoshfuji@linux-ipv6•org, dsahern@kernel•org,
flyingpeng@tencent•com, imagedong@tencent•com,
benbjiang@tencent•com
Subject: Re: [PATCH net-next] tcp_ipv6: set the drop_reason in the right place
Date: Fri, 20 May 2022 16:50:12 +0000 [thread overview]
Message-ID: <165306541200.23981.12296293606236163499.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220520021347.2270207-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 19 May 2022 19:13:47 -0700 you wrote:
> Looks like the IPv6 version of the patch under Fixes was
> a copy/paste of the IPv4 but hit the wrong spot.
> It is tcp_v6_rcv() which uses drop_reason as a boolean, and
> needs to be protected against reason == 0 before calling free.
> tcp_v6_do_rcv() has a pretty straightforward flow.
>
> Fixes: f8319dfd1b3b ("net: tcp: reset 'drop_reason' to NOT_SPCIFIED in tcp_v{4,6}_rcv()")
> Signed-off-by: Jakub Kicinski <kuba@kernel•org>
>
> [...]
Here is the summary with links:
- [net-next] tcp_ipv6: set the drop_reason in the right place
https://git.kernel.org/netdev/net-next/c/dc7769244e03
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:[~2022-05-20 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 2:13 [PATCH net-next] tcp_ipv6: set the drop_reason in the right place Jakub Kicinski
2022-05-20 16:22 ` Matthieu Baerts
2022-05-20 16:34 ` Jakub Kicinski
2022-05-20 16: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=165306541200.23981.12296293606236163499.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=benbjiang@tencent$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=flyingpeng@tencent$(echo .)com \
--cc=imagedong@tencent$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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