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

Reply: Dima Panov : "Re: linux: jid 0 pid 2834 (ThreadPoolSingl): unsupported TCP socket option TCP_INFO"
In reply to: ft : "linux: jid 0 pid 2834 (ThreadPoolSingl): unsupported TCP socket option TCP_INFO"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Kurt Jaeger <pi_at_freebsd.org>
Date: Wed, 01 Nov 2023 08:29:19 UTC

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 ?