netdev - Re: [PATCH net-next v2] net_tstamp: add SOF_TIMESTAMPING_OPT_ID

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: <167055901683.13279.3992701252219142991.git-patchwork-notify@kernel.org>
Date:   Fri, 09 Dec 2022 04:10:16 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        edumazet@...gle.com, pabeni@...hat.com, soheil@...gle.com,
        sotodel@...a.com, willemb@...gle.com
Subject: Re: [PATCH net-next v2] net_tstamp: add SOF_TIMESTAMPING_OPT_ID_TCP

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:

On Wed,  7 Dec 2022 09:37:01 -0500 you wrote:
> From: Willem de Bruijn <willemb@...gle.com>
> 
> Add an option to initialize SOF_TIMESTAMPING_OPT_ID for TCP from
> write_seq sockets instead of snd_una.
> 
> This should have been the behavior from the start. Because processes
> may now exist that rely on the established behavior, do not change
> behavior of the existing option, but add the right behavior with a new
> flag. It is encouraged to always set SOF_TIMESTAMPING_OPT_ID_TCP on
> stream sockets along with the existing SOF_TIMESTAMPING_OPT_ID.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net_tstamp: add SOF_TIMESTAMPING_OPT_ID_TCP
    https://git.kernel.org/netdev/net-next/c/b534dc46c8ae

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