Date: Wed, 1 Nov 2023 09:29:19 +0100 From: Kurt Jaeger <pi@freebsd.org> To: ft <ml@ft-c.de> Cc: stable@freebsd.org Subject: Re: linux: jid 0 pid 2834 (ThreadPoolSingl): unsupported TCP socket option TCP_INFO Message-ID: <ZUIMXz23Bej5G7hT@fc.opsec.eu> In-Reply-To: <5a677e1de51c11cb5ebab9cd139e6598558111cc.camel@ft-c.de> References: <5a677e1de51c11cb5ebab9cd139e6598558111cc.camel@ft-c.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi!
> I get many many dmesg messages:
> linux: jid 0 pid 2834 (ThreadPoolSingl): unsupported TCP socket option
> TCP_INFO (11)
[...]
> What should I do.
On FreeBSD:
man tcp
says:
TCP_INFO Information about a socket's underlying TCP session
may be retrieved by passing the read-only option
TCP_INFO to getsockopt(2). It accepts a single
argument: a pointer to an instance of struct
tcp_info.
This API is subject to change; consult the source
to determine which fields are currently filled out
by this option. FreeBSD specific additions include
send window size, receive window size, and
bandwidth-controlled window space.
On Debian:
man tcp
says:
TCP_INFO (since Linux 2.4)
Used to collect information about this socket. The kernel re-
turns a struct tcp_info as defined in the file /usr/in-
clude/linux/tcp.h. This option should not be used in code in-
tended to be portable.
So maybe start searching in the code what/why that call happens
and what it really meant (on both systems).
--
pi@FreeBSD.org +49 171 3101372 Now what ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZUIMXz23Bej5G7hT>