From: Steven Rostedt <rostedt@goodmis.org>
To: Oscar Carter <oscar.carter@gmx.com>
Cc: Ingo Molnar <mingo@redhat.com>, Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com, Jann Horn <jannh@google.com>
Subject: Re: [PATCH v2 2/2] kernel/trace: Remove function callback casts
Date: Fri, 24 Jul 2020 13:36:56 -0400 [thread overview]
Message-ID: <20200724133656.76c75629@oasis.local.home> (raw)
In-Reply-To: <20200724171418.GB3123@ubuntu>
On Fri, 24 Jul 2020 19:14:18 +0200
Oscar Carter <oscar.carter@gmx.com> wrote:
> > The linker trick should only affect architectures that don't implement
> > the needed features. I can make it so the linker trick is only applied
> > to those archs, and other archs that want more protection only need to
> > add these features to their architectures.
>
> > It's much less intrusive than this patch.
>
> Sorry, but I don't understand your proposal. What features an arch need to
> add if want the CFI protection?
The better question is, what features should an arch add to not need
the linker trick ;-)
That is, they need to change it so that they add the two parameters
that is expected by the ftrace core code. Once they do that, then they
don't need to use the linker trick, and no function typecast is needed.
In other-words, if they support the ftrace_ops and regs passing, they
can define ARCH_SUPPORTS_FTRACE_OPS. Note, they don't even really need
to support the regs, (can just send NULL), if they don't have
HAVE_DYNAMIC_FTRACE_WITH_REGS.
Which BTW, is supported by the following architectures:
arm
arm64
csky
parisc
powerpc
riscv
s390
x86
All of the above architectures should not even be hitting the code that
does the function cast. What architecture are you doing all this for?
-- Steve
next prev parent reply other threads:[~2020-07-24 17:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 15:50 [PATCH v2 0/2] kernel/trace: Remove function callback casts Oscar Carter
2020-07-19 15:50 ` [PATCH v2 1/2] kernel/trace: Prepare to remove " Oscar Carter
2020-07-19 15:50 ` [PATCH v2 2/2] kernel/trace: Remove " Oscar Carter
2020-07-21 18:05 ` Steven Rostedt
2020-07-24 16:19 ` Oscar Carter
2020-07-24 16:35 ` Steven Rostedt
2020-07-24 17:14 ` Oscar Carter
2020-07-24 17:24 ` Oscar Carter
2020-07-24 17:36 ` Steven Rostedt [this message]
2020-07-24 17:40 ` Steven Rostedt
2020-07-24 17:48 ` Steven Rostedt
2020-07-24 17:55 ` Oscar Carter
2020-07-24 18:34 ` Steven Rostedt
2020-07-25 15:09 ` Oscar Carter
2020-07-25 15:19 ` Oscar Carter
2020-07-26 15:52 ` Oscar Carter
2020-07-27 13:53 ` Steven Rostedt
2020-07-31 14:41 ` Oscar Carter
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=20200724133656.76c75629@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oscar.carter@gmx.com \
/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.