From nobody Wed Nov  1 08:29:19 2023
X-Original-To: stable@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SL0Xx4yw6z500Xq
	for <stable@mlmmj.nyi.freebsd.org>; Wed,  1 Nov 2023 08:29:21 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4SL0Xx3Cc4z3Dj0
	for <stable@freebsd.org>; Wed,  1 Nov 2023 08:29:21 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Authentication-Results: mx1.freebsd.org;
	none
Received: from pi by fc.opsec.eu with local (Exim 4.96.2 (FreeBSD))
	(envelope-from <pi@freebsd.org>)
	id 1qy6bH-0009CN-1S;
	Wed, 01 Nov 2023 09:29:19 +0100
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>
References: <5a677e1de51c11cb5ebab9cd139e6598558111cc.camel@ft-c.de>
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-stable
List-Help: <mailto:stable+help@freebsd.org>
List-Post: <mailto:stable@freebsd.org>
List-Subscribe: <mailto:stable+subscribe@freebsd.org>
List-Unsubscribe: <mailto:stable+unsubscribe@freebsd.org>
Sender: owner-freebsd-stable@freebsd.org
X-BeenThere: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5a677e1de51c11cb5ebab9cd139e6598558111cc.camel@ft-c.de>
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-Rspamd-Queue-Id: 4SL0Xx3Cc4z3Dj0

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 ?