Re: linux: jid 0 pid 2834 (ThreadPoolSingl): unsupported TCP socket option TCP_INFO

Moin-moin!


Linuxolator compat layer missed any TCP_INFO translation between BSD <=> Linux ABI and have only this debug message (unsupported TCP socket option TCP_INFO (11).)
Someone with proper skill needs to implement this layer.

On 01.11.2023 11:29, Kurt Jaeger wrote:
> 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).
> 

-- 
Sincerely,
Dima (fluffy@FreeBSD.org, https://t.me/FluffyBSD)
(desktop, kde, x11, office, ports-secteam)@FreeBSD team