From: Alex Austin <alex.austin@amd.com>
To: <netdev@vger.kernel.org>
Cc: <andrew+netdev@lunn.ch>, <bhutchings@solarflare.com>,
<davem@davemloft.net>, <ecree.xilinx@gmail.com>,
<edumazet@kernel.org>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-net-drivers@amd.com>,
<pabeni@redhat.com>, <richardcochran@gmail.com>,
<smhodgson@solarflare.com>, <alucero@amd.com>,
<pieter.jansen-van-vuuren@amd.com>,
Alex Austin <alex.austin@amd.com>
Subject: [PATCH net 0/2] sfc: fix PTP synchronization races
Date: Fri, 9 Oct 2026 19:32:38 +0100 [thread overview]
Message-ID: <20261009183240.1898762-1-alex.austin@amd.com> (raw)
This series fixes PTP synchronization races found by code inspection.
efx_ptp_pps_worker() and the SIOCSHWTSTAMP path through
efx_ptp_change_mode() both call efx_ptp_synchronize(). Concurrent calls
can interfere with the shared DMA handshake and synchronization state.
PHC adjustments can also change the clock during a capture. Patch 1
serializes synchronization transactions and PHC operations. Patch 2
returns the PPS timestamp in caller-owned storage to prevent concurrent
synchronization from overwriting it while the PPS worker reads it.
Alex Austin (2):
sfc: ptp: serialize host and MC synchronization transactions
sfc: ptp: avoid racing PPS timestamp updates
drivers/net/ethernet/sfc/ptp.c | 136 ++++++++++++++++++++++-----------
1 file changed, 90 insertions(+), 46 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-09 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 18:32 Alex Austin [this message]
2026-10-09 18:32 ` [PATCH net 1/2] sfc: ptp: serialize host and MC synchronization transactions Alex Austin
2026-10-10 19:10 ` netdev-bot+sashiko
2026-10-09 18:32 ` [PATCH net 2/2] sfc: ptp: avoid racing PPS timestamp updates Alex Austin
2026-10-10 19:10 ` netdev-bot+sashiko
2026-10-09 18:35 ` [PATCH net 0/2] sfc: fix PTP synchronization races netdev-bot+sinfo
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=20261009183240.1898762-1-alex.austin@amd.com \
--to=alex.austin@amd.com \
--cc=alucero@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=richardcochran@gmail.com \
--cc=smhodgson@solarflare.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®