From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, pabeni@redhat.com, vladimir.oltean@nxp.com,
rmk+kernel@armlinux.org.uk, kuba@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net v5] ptp: ocp: fix resource freeing order
Date: Wed, 10 Jun 2026 02:50:05 +0000 [thread overview]
Message-ID: <178105980539.2805596.14452078462884649454.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260608155952.240304-1-vadim.fedorenko@linux.dev>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 8 Jun 2026 15:59:52 +0000 you wrote:
> Commit a60fc3294a37 ("ptp: rework ptp_clock_unregister() to disable
> events") added a call to ptp_disable_all_events() which changes the
> configuration of pins if they support EXTTS events. In ptp_ocp_detach()
> pins resources are freed before ptp_clock_unregister() and it leads to
> use-after-free during driver removal. Fix it by changing the order of
> free/unregister calls. To avoid irq handler running on the other core
> while ptp device unregistering, call synchronize_irq() after HW is
> configured to stop producing irqs and no irqs are in-flight.
>
> [...]
Here is the summary with links:
- [net,v5] ptp: ocp: fix resource freeing order
https://git.kernel.org/netdev/net/c/627366c51145
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-06-10 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 15:59 [PATCH net v5] ptp: ocp: fix resource freeing order Vadim Fedorenko
2026-06-10 2: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=178105980539.2805596.14452078462884649454.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@nxp.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