From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, alan.brady@intel.com,
netdev@vger.kernel.org, yoshfuji@linux-ipv6.org,
dsahern@kernel.org, gurucharanx.g@intel.com
Subject: Re: [PATCH net-next v2 1/1] ping: support ipv6 ping socket flow labels
Date: Fri, 22 Jul 2022 11:50:14 +0000 [thread overview]
Message-ID: <165849061412.6358.11471823288314773131.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220720181310.1719994-1-anthony.l.nguyen@intel.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 20 Jul 2022 11:13:10 -0700 you wrote:
> From: Alan Brady <alan.brady@intel.com>
>
> Ping sockets don't appear to make any attempt to preserve flow labels
> created and set by userspace using IPV6_FLOWINFO_SEND. Instead they are
> clobbered by autolabels (if enabled) or zero.
>
> Grab the flowlabel out of the msghdr similar to how rawv6_sendmsg does
> it and move the memset up so it doesn't get zeroed after.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/1] ping: support ipv6 ping socket flow labels
https://git.kernel.org/netdev/net-next/c/16576a034c4b
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-07-22 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 18:13 [PATCH net-next v2 1/1] ping: support ipv6 ping socket flow labels Tony Nguyen
2022-07-22 11: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=165849061412.6358.11471823288314773131.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.brady@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gurucharanx.g@intel.com \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).