From: patchwork-bot+netdevbpf@kernel.org
To: Petr Malat <oss@malat.biz>
Cc: netdev@vger.kernel.org, vyasevich@gmail.com,
nhorman@tuxdriver.com, davem@davemloft.net, kuba@kernel.org,
linux-sctp@vger.kernel.org, marcelo.leitner@gmail.com
Subject: Re: [PATCH] sctp: Initialize daddr on peeled off socket
Date: Tue, 12 Apr 2022 03:40:11 +0000 [thread overview]
Message-ID: <164973481134.21815.13991525286598495841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220409063611.673193-1-oss@malat.biz>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 9 Apr 2022 08:36:11 +0200 you wrote:
> Function sctp_do_peeloff() wrongly initializes daddr of the original
> socket instead of the peeled off socket, which makes getpeername()
> return zeroes instead of the primary address. Initialize the new socket
> instead.
>
> Fixes: d570ee490fb1 ("[SCTP]: Correctly set daddr for IPv6 sockets during peeloff")
> Signed-off-by: Petr Malat <oss@malat.biz>
> Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
>
> [...]
Here is the summary with links:
- sctp: Initialize daddr on peeled off socket
https://git.kernel.org/netdev/net/c/8467dda0c265
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-12 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 19:59 [PATCH] sctp: Initialize daddr on peeled off socket Petr Malat
2022-03-07 21:33 ` Jakub Kicinski
2022-03-07 22:02 ` [PATCH v2] " Petr Malat
2022-04-08 17:34 ` Marcelo Ricardo Leitner
2022-04-09 6:36 ` [PATCH] " Petr Malat
2022-04-12 3:40 ` patchwork-bot+netdevbpf [this message]
2022-04-08 12:35 ` Petr Malat
2022-04-08 16:33 ` Jakub Kicinski
2022-04-08 17:18 ` Marcelo Ricardo Leitner
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=164973481134.21815.13991525286598495841.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=oss@malat.biz \
--cc=vyasevich@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).