netdev - Re: [PATCH net v3] net-timestamp: make sk_tskey more predictable in error path

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: 
 <170799662741.6637.15327449318403558646.git-patchwork-notify@kernel.org>
Date: Thu, 15 Feb 2024 11:30:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vadim Fedorenko <vadfed@...a.com>
Cc: vadim.fedorenko@...ux.dev, willemdebruijn.kernel@...il.com,
 luto@...capital.net, kuba@...nel.org, davem@...emloft.net,
 willemb@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH net v3] net-timestamp: make sk_tskey more predictable in error
 path

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@...hat.com>:

On Tue, 13 Feb 2024 03:04:28 -0800 you wrote:
> When SOF_TIMESTAMPING_OPT_ID is used to ambiguate timestamped datagrams,
> the sk_tskey can become unpredictable in case of any error happened
> during sendmsg(). Move increment later in the code and make decrement of
> sk_tskey in error path. This solution is still racy in case of multiple
> threads doing snedmsg() over the very same socket in parallel, but still
> makes error path much more predictable.
> 
> [...]

Here is the summary with links:
  - [net,v3] net-timestamp: make sk_tskey more predictable in error path
    https://git.kernel.org/netdev/net/c/488b6d91b071

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