Linux Trace Kernel
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Nam Cao <namcao@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	 linux-trace-kernel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	John Ogness	 <john.ogness@linutronix.de>
Subject: Re: [PATCH] rv/rtapp/wakeup: Use "rv_this" the rv_monitor variable
Date: Thu, 01 Oct 2026 08:31:38 +0200	[thread overview]
Message-ID: <e6f78faca93f92981130621d712ac05374d83b05.camel@redhat.com> (raw)
In-Reply-To: <20261001044218.3508990-1-namcao@linutronix.de>

On Thu, 2026-10-01 at 06:42 +0200, Nam Cao wrote:
> Commit d9e4c61a12dd ("rv: Use generic rv_this for the rv_monitor
> variable in LTL") renamed the rv_monitor variable to rv_this. But
> rtapp/wakeup monitor was late to the party and missed that.
> 
> So for this monitor, rv_this is an empty struct. The reactor fails to
> work, because rv_react() checks monitor->react and sees NULL.
> 
> Correct to "rv_this" and make the reactor work again.
> 
> Signed-off-by: Nam Cao <namcao@linutronix.de>

Damn.. Thanks for noticing!

That's a weird one, I cannot think of a way to only declare the rv_this, so the
compiler is perfectly happy to give you the empty one..

I'm taking this, but I believe it deserves the Fixes tag. What do you think?

Thanks,
Gabriele

> ---
>  kernel/trace/rv/monitors/wakeup/wakeup.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/trace/rv/monitors/wakeup/wakeup.c
> b/kernel/trace/rv/monitors/wakeup/wakeup.c
> index 01b47416f24e..2e803e79181e 100644
> --- a/kernel/trace/rv/monitors/wakeup/wakeup.c
> +++ b/kernel/trace/rv/monitors/wakeup/wakeup.c
> @@ -128,7 +128,7 @@ static void disable_wakeup(void)
>  	ltl_monitor_destroy();
>  }
>  
> -static struct rv_monitor rv_wakeup = {
> +static struct rv_monitor rv_this = {
>  	.name = "wakeup",
>  	.description = "Monitor that real-time tasks are not woken by lower-
> priority tasks",
>  	.enable = enable_wakeup,
> @@ -137,12 +137,12 @@ static struct rv_monitor rv_wakeup = {
>  
>  static int __init register_wakeup(void)
>  {
> -	return rv_register_monitor(&rv_wakeup, &rv_rtapp);
> +	return rv_register_monitor(&rv_this, &rv_rtapp);
>  }
>  
>  static void __exit unregister_wakeup(void)
>  {
> -	rv_unregister_monitor(&rv_wakeup);
> +	rv_unregister_monitor(&rv_this);
>  }
>  
>  module_init(register_wakeup);


  reply	other threads:[~2026-10-01  6:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  4:42 [PATCH] rv/rtapp/wakeup: Use "rv_this" the rv_monitor variable Nam Cao
2026-10-01  6:31 ` Gabriele Monaco [this message]
2026-10-01 11:17   ` Gabriele Monaco
2026-10-02 15:33     ` Nam Cao

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=e6f78faca93f92981130621d712ac05374d83b05.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=namcao@linutronix.de \
    --cc=rostedt@goodmis.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