From: patchwork-bot+netdevbpf@kernel.org
To: Yu Zhang <yuz08559@gmail.com>
Cc: richardcochran@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked
Date: Fri, 30 Oct 2026 23:20:19 +0000 [thread overview]
Message-ID: <179340241979.1826218.15128975775519489276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026100535.68114-1-yuz08559@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Oct 2026 20:05:35 +1000 you wrote:
> extts_fifo_show() walks ptp->tsevqs with list_count_nodes() and then
> list_first_entry() without holding ptp->tsevqs_lock, the spinlock that
> "protects tsevqs from concurrent access". Every other accessor of the
> list honours it: ptp_open() (list_add_tail), ptp_release() (list_del
> followed by kfree of the per-fd queue), ptp_clock_release() and
> ptp_clock_event() all take tsevqs_lock. extts_fifo_show() is the only
> one that does not.
>
> [...]
Here is the summary with links:
- ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked
https://git.kernel.org/netdev/net/c/603a0c40d414
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-10-30 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 10:05 [PATCH] ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked Yu Zhang
2026-10-26 10:10 ` netdev-bot+sinfo
2026-10-30 23:20 ` 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=179340241979.1826218.15128975775519489276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yuz08559@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