From: patchwork-bot+netdevbpf@kernel.org
To: Jeongjun Park <aha310510@gmail.com>
Cc: richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, yangbo.lu@nxp.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ptp: remove ptp->n_vclocks check logic in ptp_vclock_in_use()
Date: Fri, 06 Jun 2025 01:30:29 +0000 [thread overview]
Message-ID: <174917342925.3314262.10526916646495537846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250520160717.7350-1-aha310510@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 May 2025 01:07:17 +0900 you wrote:
> There is no disagreement that we should check both ptp->is_virtual_clock
> and ptp->n_vclocks to check if the ptp virtual clock is in use.
>
> However, when we acquire ptp->n_vclocks_mux to read ptp->n_vclocks in
> ptp_vclock_in_use(), we observe a recursive lock in the call trace
> starting from n_vclocks_store().
>
> [...]
Here is the summary with links:
- [v2] ptp: remove ptp->n_vclocks check logic in ptp_vclock_in_use()
https://git.kernel.org/netdev/net/c/87f7ce260a3c
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-06-06 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 16:07 Jeongjun Park
2025-05-22 12:32 ` Richard Cochran
2025-05-22 21:50 ` Jakub Kicinski
2025-05-26 11:00 ` Jeongjun Park
2025-05-27 17:42 ` Jakub Kicinski
2025-06-04 14:10 ` Jeongjun Park
2025-06-06 1:30 ` 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=174917342925.3314262.10526916646495537846.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aha310510@gmail.com \
--cc=andrew+netdev@lunn.ch \
--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=richardcochran@gmail.com \
--cc=yangbo.lu@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
all inboxes | Powered by JetHome®