From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Latypov <dlatypov@google.com>
Cc: "Kees Cook" <keescook@chromium.org>,
"Eric Biederman" <ebiederm@xmission.com>,
"David Gow" <davidgow@google.com>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
"Magnus Groß" <magnus.gross@rwth-aachen.de>,
kunit-dev@googlegroups.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] binfmt_elf: Introduce KUnit test
Date: Tue, 1 Mar 2022 10:06:50 -0500 [thread overview]
Message-ID: <20220301100650.52db90d8@gandalf.local.home> (raw)
In-Reply-To: <CAGS_qxprS1e_f_K6bi-RvVESoPJ2yQgQVszcmcRFq_VQWduyAA@mail.gmail.com>
On Mon, 28 Feb 2022 22:42:51 -0800
Daniel Latypov <dlatypov@google.com> wrote:
> But it'd definitely be interesting to try and get klp_arch_set_pc()
> working on UML if that's a possibility!
> Speaking from ignorance, I can see this either being somewhat simple
Looking at UML, it doesn't even look like it has ftrace support. So that
would be required to do it for that arch.
For UML, I'm not sure its worth it. I don't use UML but maybe others would
want ftrace for it? As UML runs in userspace, the motivation for things like
ftrace is not as high as you have gdb to walk through everything.
That said, I'm sure it would be a fun exercise for anyone to port ftrace to
UML :-)
-- Steve
next prev parent reply other threads:[~2022-03-01 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 5:43 Kees Cook
2022-02-24 6:07 ` Daniel Latypov
2022-02-24 6:13 ` Kees Cook
2022-02-24 7:57 ` David Gow
2022-02-24 14:15 ` Steven Rostedt
2022-03-01 1:48 ` Daniel Latypov
2022-03-01 3:17 ` Kees Cook
2022-03-01 4:21 ` Steven Rostedt
2022-03-01 6:42 ` Daniel Latypov
2022-03-01 15:06 ` Steven Rostedt [this message]
2022-02-24 7:41 ` David Gow
2022-02-24 9:45 ` Alexey Dobriyan
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=20220301100650.52db90d8@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=adobriyan@gmail.com \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus.gross@rwth-aachen.de \
/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