src/sys/compat/linux/linux_socket.h, branch main

compat/linux: map TCP_USER_TIMEOUT sockopt into TCP_MAXUNACKTIME

2026-04-01T21:46:08+00:00

After reading both manual pages, our TCP_MAXUNACKTIME is fairly
similar to the TCP_USER_TIMEOUT, the only considerable difference
is ours is in seconds and linux's in milliseconds.

Round up linux's in setsockopt(2) to a next whole second and
clamp ours getter to UINT_MAX ms.

Reviewed by:	tuexen, glebius
Differential Revision: https://reviews.freebsd.org/D56168
MFC after:	2 weeks
Sponsored by:	Sippy Software, Inc.

linux(4): Drop bogus arm condition due to lack of 32-bit arm support

2023-08-17T19:57:17+00:00

MFC after:		1 month

sys: Remove $FreeBSD$: two-line .h pattern

2023-08-16T17:54:11+00:00

Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/

linux(4): Rename struct l_ifreq members names to avoid conflicts with FreeBSD

2023-03-04T09:11:38+00:00

For now we are using mixed names to access struct ifreq members, some
of Linux (ifr_name, ifr_ifindex), others of FreeBSD. To avoid conflicts
switch to use FreeBSD names.

Reviewed by:		jhibbits
Differential Revision:	https://reviews.freebsd.org/D38792

linux(4): Reduce code duplication between MD files

2023-03-04T09:11:38+00:00

Move struct ifnet definitions under compat/linux.

Reviewed by:		emaste
Differential Revision:	https://reviews.freebsd.org/D38791

linux(4): Handle IP_ORIGDSTADDR socket option for IPPROTO_IP protocol level

2022-05-28T20:47:40+00:00

MFC after:		2 weeks

linux(4): Handle SO_TIMESTAMPNS socket option

2022-05-28T20:46:05+00:00

The SO_TIMESTAMPNS enables or disables the receiving of the SCM_TIMESTAMPNS
control message. The cmsg_data field is a struct timespec.
To distinguish between SO_TIMESTAMP and SO_TIMESTAMPNS in the recvmsg()
map the last one to the SO_BINTIME and convert bintime to the timespec.
In the rest, implementation is identical to the SO_TIMESTAMP.

MFC after:		2 weeks

linux(4): Handle 64-bit SO_TIMESTAMP for 32-bit binaries

2022-05-28T20:45:39+00:00

To solve y2k38 problem in the recvmsg syscall the new SO_TIMESTAMP
constant were added on v5.1 Linux kernel. So, old 32-bit binaries
that knows only 32-bit time_t uses the old value of the constant,
and binaries that knows 64-bit time_t uses the new constant.

To determine what size of time_t type is expected by the user-space,
store requested value (SO_TIMESTAMP) in the process emuldata structure.

MFC after:		2 weeks

linux(4): For future use move SCM definitions below socket options

2022-05-28T20:42:23+00:00

MFC after:		2 weeks

linux(4): Handle SO_DOMAIN in getsockopt syscall.

2022-04-11T20:31:28+00:00

Differential revision:	https://reviews.freebsd.org/D34714