From: Martin Kaiser <martin@kaiser.cx>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: eprobe: read the complete FILTER_PTR_STRING pointer
Date: Fri, 26 Jun 2026 12:20:36 +0200 [thread overview]
Message-ID: <aj5SdK9gUIVoPmmE@akranes.kaiser.cx> (raw)
In-Reply-To: <20260626055440.76c28d25@fedora>
Thus wrote Steven Rostedt (rostedt@goodmis.org):
> On Mon, 22 Jun 2026 12:58:15 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> > The problem is that the event does not provide the information that
> > the string is in user space or not. But actually, for syscall events
> > all data pointed by syscall parameter should be in the user space.
> I think we should make this work then:
> echo 'e:open syscalls.sys_enter_openat file=+u0($filename):ustring' > dynamic_events
> That is, to have +u0() say "this is going to be dereferencing user space".
> I'll add Martin's patch and see if it makes the above work.
I've just tried your command with my patch. It works for me, filenames are
logged correctly.
Martin
> -- Steve
next prev parent reply other threads:[~2026-06-26 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 14:54 [PATCH] tracing: eprobe: read the complete FILTER_PTR_STRING pointer Martin Kaiser
2026-06-16 2:09 ` Masami Hiramatsu
2026-06-17 8:32 ` Martin Kaiser
2026-06-18 1:52 ` Masami Hiramatsu
2026-06-20 15:05 ` Martin Kaiser
2026-06-22 3:58 ` Masami Hiramatsu
2026-06-26 9:54 ` Steven Rostedt
2026-06-26 10:20 ` Martin Kaiser [this message]
2026-06-26 10:42 ` Steven Rostedt
2026-06-26 15:45 ` Masami Hiramatsu
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=aj5SdK9gUIVoPmmE@akranes.kaiser.cx \
--to=martin@kaiser.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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