[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241107110417.7850d68f@gandalf.local.home>
Date: Thu, 7 Nov 2024 11:04:17 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: Marco Elver <elver@...gle.com>, Kees Cook <keescook@...omium.org>,
Masami Hiramatsu <mhiramat@...nel.org>, Andrew Morton
<akpm@...ux-foundation.org>, Oleg Nesterov <oleg@...hat.com>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Dmitry
Vyukov <dvyukov@...gle.com>, kasan-dev@...glegroups.com
Subject: Re: [PATCH v2 1/2] tracing: Add task_prctl_unknown tracepoint
On Thu, 7 Nov 2024 10:52:37 -0500
Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:
> I suspect you base the overhead analysis on the x86-64 implementation
> of sys_enter/exit tracepoint and especially the overhead caused by
> the SYSCALL_WORK_SYSCALL_TRACEPOINT thread flag, am I correct ?
>
> If that is causing a too large overhead, we should investigate if
> those can be improved instead of adding tracepoints in the
> implementation of system calls.
That would be great to get better, but the reason I'm not against this
patch is because prctl() is not a normal system call. It's basically an
ioctl() for Linux, and very vague. It's basically the garbage system call
when you don't know what to do. It's even being proposed for the sframe
work.
I understand your sentiment and agree. I don't want any random system call
to get a tracepoint attached to it. But here I'd make an exception.
-- Steve
Powered by blists - more mailing lists