From: patchwork-bot+netdevbpf@kernel.org
To: Aksh Garg <a-garg7@ti.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, edumazet@google.com,
linux-kernel@vger.kernel.org, c-vankar@ti.com,
s-vadapalli@ti.com, danishanwar@ti.com
Subject: Re: [PATCH net v2] net: ethernet: ti: am65-cpts: fix timestamp loss due to race conditions
Date: Tue, 21 Oct 2025 11:00:06 +0000 [thread overview]
Message-ID: <176104440629.1025140.2694526170701445525.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251016115755.1123646-1-a-garg7@ti.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 16 Oct 2025 17:27:55 +0530 you wrote:
> Resolve race conditions in timestamp events list handling between TX
> and RX paths causing missed timestamps.
>
> The current implementation uses a single events list for both TX and RX
> timestamps. The am65_cpts_find_ts() function acquires the lock,
> splices all events (TX as well as RX events) to a temporary list,
> and releases the lock. This function performs matching of timestamps
> for TX packets only. Before it acquires the lock again to put the
> non-TX events back to the main events list, a concurrent RX
> processing thread could acquire the lock (as observed in practice),
> find an empty events list, and fail to attach timestamp to it,
> even though a relevant event exists in the spliced list which is yet to
> be restored to the main list.
>
> [...]
Here is the summary with links:
- [net,v2] net: ethernet: ti: am65-cpts: fix timestamp loss due to race conditions
https://git.kernel.org/netdev/net/c/49d34f3dd851
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:[~2025-10-21 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 11:57 Aksh Garg
2025-10-16 12:04 ` Siddharth Vadapalli
2025-10-21 11:00 ` 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=176104440629.1025140.2694526170701445525.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a-garg7@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=c-vankar@ti.com \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s-vadapalli@ti.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
all inboxes | Powered by JetHome®