From nobody Fri Dec 26 15:23:00 2025 Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4C3EB18C31; Thu, 4 Jan 2024 08:58:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=corelatus.se Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=corelatus.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=corelatus.se header.i=@corelatus.se header.b="hfEuH+Ch"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="9bnB67Y/" Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 5B9343200B8F; Thu, 4 Jan 2024 03:58:43 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 04 Jan 2024 03:58:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=corelatus.se; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:subject:subject:to :to; s=fm1; t=1704358722; x=1704445122; bh=/Z5C3JxfHNpoAjvvAcHhD mbyTXDu4B/UNHLYNTCyyOE=; b=hfEuH+ChLsjSk3N51fYhtm5AiDWaWOHk1jhKs apM1OTUIwllA0t8K1DLKWosXVCQqhABWW29iNdc5E2c8HxbeZOsYUMkM2adsnmHL etzHVzeE9aoUJ3z9zh5N2y/kvCgG70sFJQ5isZr1YOIQEJen9LDuAhF7pqs+Vaf1 YyV2kTjL3GRM7g54L68pQTVeyTgGLRLD73MhEP1IlrUYA8zWbJuZYgrk39HUecUT LHJmR93xqNzI4GhAWO0CVTBYCA43RLnpsWMUaQCGxALoqVEh+dCqHRZ9YMlW7YLc kbml8ee3Pwv3T29vUo5HlWXBCUCY4U8BwH5JAdzEZ6sb/G3MQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1704358722; x=1704445122; bh=/Z5C3JxfHNpoAjvvAcHhDmbyTXDu 4B/UNHLYNTCyyOE=; b=9bnB67Y/ea3yYp8QD6L1/UTUORth69DAuXyCvZo8Q9pn JUNxbWHqv2Z4HIL0kT0FzgHX/n15N+sayRtvOz7E1sfeD4UefR0GXYb0rIAbXeKI MoHyoM5IEDfnabehUgdGBTH0k4ycQFeiR/EqqwvqJyV4x5qxVwuErC3OGS2zesjF D/+xpk3ZZ7QtIvTFGR9oKn4neCs5Y1KJeLpT6Nltug9tPJCS3WwuQcHOj5L1Wy1h foNJvdodfziQQa9xX/kiVJvhu6vWXWGL8Na1oL7ukpnrznT+VfLjHdfqAmJY/DTe H6fnHncZaeeGagEAgQsXLBd7ndpT4mJRNnAaRh4J4A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdegiedguddvgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhephffvvefufffkofgggfestdekre dtredttdenucfhrhhomhepvfhhohhmrghsucfnrghnghgvuceothhhohhmrghssegtohhr vghlrghtuhhsrdhsvgeqnecuggftrfgrthhtvghrnhepjefgffdvgeekieehheefheekud euvdelueeltdefjeekjeegueeugeelkeeijeeknecuffhomhgrihhnpehkvghrnhgvlhdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hthhhomhgrshestghorhgvlhgrthhushdrtghomh X-ME-Proxy: Feedback-ID: ia69946ac:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 4 Jan 2024 03:58:42 -0500 (EST) Received: from thomas by k2.corelatus.se with local (Exim 4.96) (envelope-from ) id 1rLJYl-000Cnh-0e; Thu, 04 Jan 2024 09:58:39 +0100 From: Thomas Lange To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Cc: willemdebruijn.kernel@gmail.com, jthinz@mailbox.tu-berlin.de, arnd@arndb.de, deepa.kernel@gmail.com, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, Thomas Lange Subject: [PATCH RESEND net] net: Implement missing SO_TIMESTAMPING_NEW cmsg support Date: Thu, 4 Jan 2024 09:57:44 +0100 Message-Id: <20240104085744.49164-1-thomas@corelatus.se> X-Mailer: git-send-email 2.39.2 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Commit 9718475e6908 ("socket: Add SO_TIMESTAMPING_NEW") added the new socket option SO_TIMESTAMPING_NEW. However, it was never implemented in __sock_cmsg_send thus breaking SO_TIMESTAMPING cmsg for platforms using SO_TIMESTAMPING_NEW. Fixes: 9718475e6908 ("socket: Add SO_TIMESTAMPING_NEW") Link: https://lore.kernel.org/netdev/6a7281bf-bc4a-4f75-bb88-7011908ae471@a= pp.fastmail.com/ Signed-off-by: Thomas Lange Reviewed-by: Willem de Bruijn --- net/core/sock.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/core/sock.c b/net/core/sock.c index 51d52859e942..d02534c77413 100644 --- a/net/core/sock.c +++ b/net/core/sock.c @@ -2813,6 +2813,7 @@ int __sock_cmsg_send(struct sock *sk, struct cmsghdr = *cmsg, sockc->mark =3D *(u32 *)CMSG_DATA(cmsg); break; case SO_TIMESTAMPING_OLD: + case SO_TIMESTAMPING_NEW: if (cmsg->cmsg_len !=3D CMSG_LEN(sizeof(u32))) return -EINVAL; =20 --=20 2.39.2