kernel/tools/testing/selftests/net/ipv6_flowlabel.c, branch linux-6.2.yHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-6.2.y2022-07-22T11:40:27Zping: support ipv6 ping socket flow labels2022-07-22T11:40:27ZAlan Bradyalan.brady@intel.com2022-07-20T18:13:10Zurn:sha1:16576a034c4ba2e3179f48554d4f1bd5c05382cd
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.
Signed-off-by: Alan Brady <alan.brady@intel.com>
Tested-by: Gurucharan <gurucharanx.g@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
selftests/net: ipv6 flowlabel2019-05-29T00:18:53ZWillem de Bruijnwillemb@google.com2019-05-27T20:47:51Zurn:sha1:3fb321fde22ddc3adc83e1f690b1fad9dfbd24ef
Test the IPv6 flowlabel control and datapath interfaces:
Acquire and release the right to use flowlabels with socket option
IPV6_FLOWLABEL_MGR.
Then configure flowlabels on send and read them on recv with cmsg
IPV6_FLOWINFO. Also verify auto-flowlabel if not explicitly set.
This helped identify the issue fixed in commit 95c169251bf73 ("ipv6:
invert flowlabel sharing check in process and user mode")
Signed-off-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>