netdev - Re: [PATCH] Bluetooth: increment TX timestamping tskey always for stream sockets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174371163427.2672071.7073463393326839454.git-patchwork-notify@kernel.org>
Date: Thu, 03 Apr 2025 20:20:34 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Pauli Virtanen <pav@....fi>
Cc: linux-bluetooth@...r.kernel.org, netdev@...r.kernel.org,
 willemdebruijn.kernel@...il.com, kerneljasonxing@...il.com
Subject: Re: [PATCH] Bluetooth: increment TX timestamping tskey always for stream
 sockets

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:

On Thu,  3 Apr 2025 19:57:59 +0300 you wrote:
> Documentation/networking/timestamping.rst implies TX timestamping OPT_ID
> tskey increments for each sendmsg.  In practice: TCP socket increments
> it for all sendmsg, timestamping on or off, but UDP only when
> timestamping is on. The user-visible counter resets when OPT_ID is
> turned on, so difference can be seen only if timestamping is enabled for
> some packets only (eg. via SO_TIMESTAMPING CMSG).
> 
> [...]

Here is the summary with links:
  - Bluetooth: increment TX timestamping tskey always for stream sockets
    https://git.kernel.org/bluetooth/bluetooth-next/c/2c1cf148c1fa

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html