public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	bpf@vger.kernel.org
Subject: Re: [PATCH v3] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast
Date: Mon, 8 Dec 2025 04:43:52 -0500	[thread overview]
Message-ID: <20251208044352.38360456@debian> (raw)
In-Reply-To: <e2fe3162-4b7b-44d6-91ff-f439b3dce706@paulmck-laptop>

On Sun, 7 Dec 2025 20:20:23 -0800
"Paul E. McKenney" <paulmck@kernel.org> wrote:

> [ paulmck: Remove trace_syscalls.h changes per Steven Rostedt. ]

But they still need to be fixed.

With PREEMPT_RT enabled:

 # trace-cmd start -e syscalls
 # trace-cmd show
            bash-1165    [001] DBZ.f   269.955644: sys_ioctl(fd: 0xff, cmd: 0x5413, arg: 0x7fffd3d6a2d0)
            bash-1165    [001] DBZ.f   269.955649: sys_ioctl -> 0x0
            bash-1165    [001] DBZ.f   269.955694: sys_rt_sigprocmask(how: 2, nset: 0x7fffd3d6a3a0, oset: 0, sigsetsize: 8)
            bash-1165    [001] DBZ.f   269.955698: sys_rt_sigprocmask -> 0x0
            bash-1165    [001] DBZ.f   269.955715: sys_wait4(upid: 0xffffffffffffffff, stat_addr: 0x7fffd3d69c50, options: 0xb, ru: 0)
            bash-1165    [001] DBZ.f   269.955722: sys_wait4 -> 0xfffffffffffffff6
            bash-1165    [001] DBZ.f   269.955725: sys_rt_sigreturn()
            bash-1165    [001] DBZ.f   269.955758: sys_rt_sigaction(sig: 2, act: 0x7fffd3d6a2e0, oact: 0x7fffd3d6a380, sigsetsize: 8)
            bash-1165    [001] DBZ.f   269.955762: sys_rt_sigaction -> 0x0
                               ^^^^^
                            This is just garbage.

-- Steve

  reply	other threads:[~2025-12-08  9:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  4:20 [PATCH v3] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast Paul E. McKenney
2025-12-08  9:43 ` Steven Rostedt [this message]
2025-12-08 20:46   ` Paul E. McKenney
2025-12-09  0:38     ` Steven Rostedt
2025-12-09 22:29       ` Paul E. McKenney
2025-12-10  3:11         ` Steven Rostedt
2025-12-11 20:02 ` Joel Fernandes
2025-12-11 20:23   ` Paul E. McKenney
2025-12-12  0:12     ` Joel Fernandes
2025-12-12  0:47       ` Paul E. McKenney
2025-12-12  3:43         ` Joel Fernandes
2025-12-12  7:50           ` Paul E. McKenney
2025-12-12  9:28             ` Joel Fernandes
2025-12-12 23:10               ` Paul E. McKenney
2025-12-12 23:54                 ` Joel Fernandes
2025-12-13  0:06                   ` Paul E. McKenney
2025-12-13  2:18                     ` Steven Rostedt
2025-12-13  4:19                       ` Mathieu Desnoyers
2025-12-13  6:20                         ` Steven Rostedt
2025-12-12  1:13     ` Steven Rostedt

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=20251208044352.38360456@debian \
    --to=rostedt@goodmis.org \
    --cc=bigeasy@linutronix.de \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@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