From: Gabriele Monaco <gmonaco@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Wen Yang <wen.yang@linux.dev>, Nam Cao <namcao@linutronix.de>
Subject: Re: [PATCH v4 12/13] rv: Fix read_lock scope in per-task DA cleanup
Date: Thu, 02 Jul 2026 08:31:21 +0200 [thread overview]
Message-ID: <9b349d2c33e356e735050ddbb6fd005b8870a7d7.camel@redhat.com> (raw)
In-Reply-To: <20260701152705.6dc9d8f2@gandalf.local.home>
On Wed, 2026-07-01 at 15:27 -0400, Steven Rostedt wrote:
> On Mon, 1 Jun 2026 17:38:39 +0200
> Gabriele Monaco <gmonaco@redhat.com> wrote:
>
> > The da_monitor_reset_all() function for per-task monitors takes
> > tasklist_lock while iterating over tasks, then keeps it also while
> > iterating over idle tasks (one per CPU). The latter is not necessary
> > since the lock needs to guard only for_each_process_thread().
> >
> > Use a scoped_guard for more compact syntax and adjust the scope only
> > where the lock is necessary.
> >
> > Reviewed-by: Wen Yang <wen.yang@linux.dev>
> > Reviewed-by: Nam Cao <namcao@linutronix.de>
> > Signed-off-by: Gabriele Monaco <gmonaco@redhat.com>
>
> Hmm, this and patch 13 didn't get applied. Do you plan on sending them later?
Yes, I didn't add them to the pull request since they weren't quite fixes, then
ended up not sending a "normal" pull request for 7.2 just for these.
I'm going to put them together for the next round.
Thanks,
Gabriele
next prev parent reply other threads:[~2026-07-02 6:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 15:38 [PATCH v4 00/13] rv: Fixes on Deterministic and Hybrid Automata Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 01/13] rv: Fix __user specifier usage in extract_params() Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 02/13] rv: Reset per-task DA monitors before releasing the slot Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 03/13] rv: Prevent in-flight per-task handlers from using invalid slots Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 04/13] rv: Ensure all pending probes terminate on per-obj monitor destroy Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 05/13] rv: Fix monitor start ordering and memory ordering for monitoring flag Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 06/13] rv: Do not rely on clean monitor when initialising HA Gabriele Monaco
2026-06-02 8:52 ` Nam Cao
2026-06-01 15:38 ` [PATCH v4 07/13] rv: Add automatic cleanup handlers for per-task HA monitors Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 08/13] rv: Ensure synchronous cleanup for " Gabriele Monaco
2026-06-02 9:17 ` Nam Cao
2026-06-01 15:38 ` [PATCH v4 09/13] rv: Prevent task migration while handling per-CPU events Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 10/13] rv: Use 0 to check preemption enabled in opid Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 11/13] verification/rvgen: Fix suffix strip in dot2k Gabriele Monaco
2026-06-01 15:38 ` [PATCH v4 12/13] rv: Fix read_lock scope in per-task DA cleanup Gabriele Monaco
2026-07-01 19:27 ` Steven Rostedt
2026-07-02 6:31 ` Gabriele Monaco [this message]
2026-06-01 15:38 ` [PATCH v4 13/13] verification/rvgen: Generate cleanup hook for per-obj monitor Gabriele Monaco
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=9b349d2c33e356e735050ddbb6fd005b8870a7d7.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=rostedt@goodmis.org \
--cc=wen.yang@linux.dev \
/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