mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Florian Westphal <fw@strlen.de>,
	netdev@vger.kernel.org, mptcp@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	stable@vger.kernel.org, Clark Williams <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Hannes Reinecke <hare@kernel.org>,
	linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net 09/10] mptcp: pm: avoid sleeping while holding rcu_read_lock
Date: Mon, 1 Jun 2026 17:27:21 +1000	[thread overview]
Message-ID: <1e11dea6-a9a4-425e-a31b-ab5f8561f3b8@kernel.org> (raw)
In-Reply-To: <20260601065813.Z8V8Tb6d@linutronix.de>

Hi Sebastian,

Thank you for the review!

On 01/06/2026 16:58, Sebastian Andrzej Siewior wrote:
> On 2026-06-01 13:10:05 [+1000], Matthieu Baerts (NGI0) wrote:
>> sk_stop_timer_sync() calls del_timer_sync(), which spin-waits for the
> There is no del_timer_sync()

Indeed, not sure why I put that one. I wanted to say timer_delete_sync()

>> timer callback to complete on non-RT kernels. But on PREEMPT_RT, it can
>> sleep. Sleeping inside an RCU read-side critical section might trigger a
>> lockdep splat.
> 
> It can not sleep. timer_delete_sync() does not sleep. It can block on
> spinlock_t and schedule but this is okay within a RCU read section.

Sorry, I got confused by the comment in __timer_delete_sync().

> Do you have a report for this?
No, sorry. I was exploring the code in timer.c after a related comment
from Sashiko [1]. I noticed the comment in __timer_delete_sync() about
being able to sleep on PREEMPT_RT, then saw that timer_delete_sync() was
called inside a rcu_read_lock(), and I thought it was wrong. I should
have tried to reproduce the warning on PREEMPT_RT, but I switched to the
next bug instead :-/

Sorry for the noise, let's drop this patch if it is not needed then.

[1] https://github.com/multipath-tcp/mptcp_net-next/issues/623

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2026-06-01  7:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  3:09 [PATCH net 00/10] mptcp: misc fixes for v7.1-rc7 Matthieu Baerts (NGI0)
2026-06-01  3:09 ` [PATCH net 01/10] mptcp: fix missing wakeups in edge scenarios Matthieu Baerts (NGI0)
2026-06-01  3:09 ` [PATCH net 02/10] mptcp: fix retransmission loop when csum is enabled Matthieu Baerts (NGI0)
2026-06-01  3:09 ` [PATCH net 03/10] mptcp: close TOCTOU race while computing rcv_wnd Matthieu Baerts (NGI0)
2026-06-01  3:10 ` [PATCH net 04/10] mptcp: allow subflow rcv wnd to shrink Matthieu Baerts (NGI0)
2026-06-01  3:10 ` [PATCH net 05/10] mptcp: pm: fix extra_subflows underflow on userspace PM subflow creation Matthieu Baerts (NGI0)
2026-06-01  3:10 ` [PATCH net 06/10] selftests: mptcp: add test for extra_subflows underflow on userspace PM Matthieu Baerts (NGI0)
2026-06-01  3:10 ` [PATCH net 07/10] mptcp: sockopt: check timestamping ret value Matthieu Baerts (NGI0)
2026-06-01  3:10 ` [PATCH net 08/10] mptcp: sockopt: set sockopt on all subflows Matthieu Baerts (NGI0)
2026-06-01  3:10 ` [PATCH net 09/10] mptcp: pm: avoid sleeping while holding rcu_read_lock Matthieu Baerts (NGI0)
2026-06-01  6:58   ` Sebastian Andrzej Siewior
2026-06-01  7:27     ` Matthieu Baerts [this message]
2026-06-01  3:10 ` [PATCH net 10/10] mptcp: check desc->count in read_sock Matthieu Baerts (NGI0)

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=1e11dea6-a9a4-425e-a31b-ab5f8561f3b8@kernel.org \
    --to=matttbe@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=geliang@kernel.org \
    --cc=hare@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.org \
    /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®