From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadfed@meta.com>
Cc: vadim.fedorenko@linux.dev, willemdebruijn.kernel@gmail.com,
luto@amacapital.net, kuba@kernel.org, davem@davemloft.net,
willemb@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net v3] net-timestamp: make sk_tskey more predictable in error path
Date: Thu, 15 Feb 2024 11:30:27 +0000 [thread overview]
Message-ID: <170799662741.6637.15327449318403558646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240213110428.1681540-1-vadfed@meta.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.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
prev parent reply other threads:[~2024-02-15 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:04 [PATCH net v3] net-timestamp: make sk_tskey more predictable in error path Vadim Fedorenko
2024-02-13 14:47 ` Willem de Bruijn
2024-02-15 11:30 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170799662741.6637.15327449318403558646.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=vadfed@meta.com \
--cc=vadim.fedorenko@linux.dev \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox