From: Pingfan Liu <kernelfans@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Pingfan Liu <kernelfans@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: [PATCH 0/3] tracing/filter: make filter_pred_pchar() survive the access to user space
Date: Fri, 7 Jan 2022 12:49:48 +0800 [thread overview]
Message-ID: <20220107044951.22080-1-kernelfans@gmail.com> (raw)
When
echo "filename ~ \"cpu\"" > events/syscalls/sys_enter_openat/filter
echo 1 > events/syscalls/sys_enter_at/enable
The kernel will run into a #PF (see [3/3].
This series resorts to copy_from_user() to cope with the access to user
space.
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>
To: linux-kernel@vger.kernel.org
Pingfan Liu (3):
tracing/filter: degrade addr in filter_pred_string() from double
pointer to pointer
tracing/filter: harden the prototype of predicate_parse()
tracing/filter: make filter_pred_pchar() survive the access to user
space
kernel/trace/trace.h | 1 +
kernel/trace/trace_events_filter.c | 38 ++++++++++++++++++++++++------
2 files changed, 32 insertions(+), 7 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-07 4:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 4:49 Pingfan Liu [this message]
2022-01-07 4:49 ` [PATCH 1/3] tracing/filter: degrade addr in filter_pred_string() from double pointer to pointer Pingfan Liu
2022-01-07 17:18 ` Steven Rostedt
2022-01-10 2:58 ` Pingfan Liu
2022-01-07 4:49 ` [PATCH 2/3] tracing/filter: harden the prototype of predicate_parse() Pingfan Liu
2022-01-07 4:49 ` [PATCH 3/3] tracing/filter: make filter_pred_pchar() survive the access to user space Pingfan Liu
2022-01-07 22:25 ` Steven Rostedt
2022-01-08 6:49 ` kernel test robot
2022-01-08 6:49 ` kernel test robot
2022-01-08 8:20 ` kernel test robot
2022-01-08 8:20 ` kernel test robot
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=20220107044951.22080-1-kernelfans@gmail.com \
--to=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.