Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: richardcochran@gmail.com, yangbo.lu@nxp.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, ihuguet@redhat.com,
	mlichvar@redhat.com, hector.blanco.alcaine@intel.com,
	christopher.s.hall@intel.com, bigeasy@linutronix.de,
	florian.zeitz@schettke.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] ptp: vclock: Switch from RCU to SRCU
Date: Thu, 04 Jun 2026 02:10:28 +0000	[thread overview]
Message-ID: <178053902807.2204548.18128583002992277362.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260529-vclock_rcu-v2-1-02a5531fab92@linutronix.de>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 29 May 2026 19:11:47 +0200 you wrote:
> The usage of PTP vClocks leads immediately to the following issues with
> ptp4l with LOCKDEP and DEBUG_ATOMIC_SLEEP enabled: "BUG: sleeping function
> called from invalid context".
> 
> ptp_convert_timestamp() acquires a mutex_t within a RCU read section.  This
> is illegal, because acquiring a mutex_t can result in voluntary scheduling
> request which is not allowed within a RCU read section.
> 
> [...]

Here is the summary with links:
  - [net,v2] ptp: vclock: Switch from RCU to SRCU
    https://git.kernel.org/netdev/net/c/672bd0519e27

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-06-04  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 17:11 [PATCH net v2] ptp: vclock: Switch from RCU to SRCU Kurt Kanzenbach
2026-05-29 17:39 ` Sebastian Andrzej Siewior
2026-06-04  2:10 ` 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=178053902807.2204548.18128583002992277362.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bigeasy@linutronix.de \
    --cc=christopher.s.hall@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.zeitz@schettke.com \
    --cc=hector.blanco.alcaine@intel.com \
    --cc=ihuguet@redhat.com \
    --cc=kuba@kernel.org \
    --cc=kurt@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlichvar@redhat.com \
    --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