tools/testing/selftests/net/reuseport_dualstack.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/net/reuseport_dualstack.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/net/reuseport_dualstack.c- Extension
.c- Size
- 5983 bytes
- Lines
- 222
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
arpa/inet.herrno.herror.hlinux/in.hlinux/unistd.hstdio.hstdlib.hstring.hsys/epoll.hsys/types.hsys/socket.hunistd.hsched.h
Detected Declarations
function build_rcv_fdfunction send_from_v4function receive_oncefunction testfunction setup_netnsfunction main
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* It is possible to use SO_REUSEPORT to open multiple sockets bound to
* equivalent local addresses using AF_INET and AF_INET6 at the same time. If
* the AF_INET6 socket has IPV6_V6ONLY set, it's clear which socket should
* receive a given incoming packet. However, when it is not set, incoming v4
* packets should prefer the AF_INET socket(s). This behavior was defined with
* the original SO_REUSEPORT implementation, but broke with
* e32ea7e74727 ("soreuseport: fast reuseport UDP socket selection")
* This test creates these mixed AF_INET/AF_INET6 sockets and asserts the
* AF_INET preference for v4 packets.
*/
#define _GNU_SOURCE
#include <arpa/inet.h>
#include <errno.h>
#include <error.h>
#include <linux/in.h>
#include <linux/unistd.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <sys/epoll.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <unistd.h>
#include <sched.h>
static const int PORT = 8888;
static void build_rcv_fd(int family, int proto, int *rcv_fds, int count)
{
struct sockaddr_storage addr;
struct sockaddr_in *addr4;
struct sockaddr_in6 *addr6;
int opt, i;
switch (family) {
case AF_INET:
addr4 = (struct sockaddr_in *)&addr;
addr4->sin_family = AF_INET;
addr4->sin_addr.s_addr = htonl(INADDR_ANY);
addr4->sin_port = htons(PORT);
break;
case AF_INET6:
addr6 = (struct sockaddr_in6 *)&addr;
addr6->sin6_family = AF_INET6;
addr6->sin6_addr = in6addr_any;
addr6->sin6_port = htons(PORT);
break;
default:
error(1, 0, "Unsupported family %d", family);
}
for (i = 0; i < count; ++i) {
rcv_fds[i] = socket(family, proto, 0);
if (rcv_fds[i] < 0)
error(1, errno, "failed to create receive socket");
opt = 1;
if (setsockopt(rcv_fds[i], SOL_SOCKET, SO_REUSEPORT, &opt,
sizeof(opt)))
error(1, errno, "failed to set SO_REUSEPORT");
if (bind(rcv_fds[i], (struct sockaddr *)&addr, sizeof(addr)))
error(1, errno, "failed to bind receive socket");
if (proto == SOCK_STREAM && listen(rcv_fds[i], 10))
error(1, errno, "failed to listen on receive port");
}
}
static void send_from_v4(int proto)
{
struct sockaddr_in saddr, daddr;
int fd;
saddr.sin_family = AF_INET;
saddr.sin_addr.s_addr = htonl(INADDR_ANY);
saddr.sin_port = 0;
daddr.sin_family = AF_INET;
daddr.sin_addr.s_addr = htonl(INADDR_LOOPBACK);
daddr.sin_port = htons(PORT);
fd = socket(AF_INET, proto, 0);
if (fd < 0)
error(1, errno, "failed to create send socket");
Annotation
- Immediate include surface: `arpa/inet.h`, `errno.h`, `error.h`, `linux/in.h`, `linux/unistd.h`, `stdio.h`, `stdlib.h`, `string.h`.
- Detected declarations: `function build_rcv_fd`, `function send_from_v4`, `function receive_once`, `function test`, `function setup_netns`, `function main`.
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.