From: patchwork-bot+netdevbpf@kernel.org
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, mengyuanlou@net-swift.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
jacob.e.keller@intel.com, kees@kernel.org,
aleksandr.loktionov@intel.com, vadim.fedorenko@linux.dev,
sashiko-bot@kernel.org
Subject: Re: [PATCH net v3] net: libwx: fix races in Tx timestamp handling
Date: Thu, 24 Sep 2026 16:50:07 +0000 [thread overview]
Message-ID: <179026860739.1650423.11536566260145832868.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <77431AF9A0E369F3+20260921071549.1141804-1-jiawenwu@trustnetic.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Sep 2026 15:15:49 +0800 you wrote:
> wx->ptp_tx_skb is shared between the Tx path, the PTP auxiliary
> worker and the timestamp cleanup paths. The
> WX_STATE_PTP_TX_IN_PROGRESS bit prevents multiple Tx paths from
> submitting timestamp requests, but does not serialize the worker
> against cleanup.
>
> As a result, wx_ptp_clear_tx_timestamp() can free an skb after
> wx_ptp_tx_hwtstamp_work() has obtained its pointer. The worker may
> then pass the freed skb to skb_tstamp_tx() and release the same
> reference again.
>
> [...]
Here is the summary with links:
- [net,v3] net: libwx: fix races in Tx timestamp handling
https://git.kernel.org/netdev/net/c/3173cba11701
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:[~2026-09-24 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:15 [PATCH net v3] net: libwx: fix races in Tx timestamp handling Jiawen Wu
2026-09-24 16:50 ` 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=179026860739.1650423.11536566260145832868.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiawenwu@trustnetic.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sashiko-bot@kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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