From: Kees Cook <kees@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>, Kees Cook <kees@kernel.org>,
Marco Elver <elver@google.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com
Subject: Re: [PATCH v3 1/2] tracing: Add task_prctl_unknown tracepoint
Date: Mon, 16 Dec 2024 16:38:26 -0800 [thread overview]
Message-ID: <173439590402.2288303.6690589716880149969.b4-ty@kernel.org> (raw)
In-Reply-To: <20241108113455.2924361-1-elver@google.com>
On Fri, 08 Nov 2024 12:34:24 +0100, Marco Elver wrote:
> prctl() is a complex syscall which multiplexes its functionality based
> on a large set of PR_* options. Currently we count 64 such options. The
> return value of unknown options is -EINVAL, and doesn't distinguish from
> known options that were passed invalid args that also return -EINVAL.
>
> To understand if programs are attempting to use prctl() options not yet
> available on the running kernel, provide the task_prctl_unknown
> tracepoint.
>
> [...]
Applied to for-next/hardening, thanks!
[1/2] tracing: Add task_prctl_unknown tracepoint
https://git.kernel.org/kees/c/57a6baf3a3ea
[2/2] tracing: Remove pid in task_rename tracing output
https://git.kernel.org/kees/c/a6115cceb1dd
Take care,
--
Kees Cook
prev parent reply other threads:[~2024-12-17 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 11:34 Marco Elver
2024-11-08 11:34 ` [PATCH v3 2/2] tracing: Remove pid in task_rename tracing output Marco Elver
2024-11-15 12:00 ` [PATCH v3 1/2] tracing: Add task_prctl_unknown tracepoint Marco Elver
2024-11-15 13:27 ` Steven Rostedt
2024-11-15 15:06 ` Marco Elver
2024-12-11 14:09 ` Marco Elver
2024-12-12 10:05 ` Alexander Potapenko
2024-12-17 0:38 ` Kees Cook [this message]
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=173439590402.2288303.6690589716880149969.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.com \
--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
all inboxes | Powered by JetHome®