From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jann Horn <jannh@google.com>
Cc: salyzyn@google.com, Steven Rostedt <rostedt@goodmis.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Golden_Miller83@protonmail.ch, Greg KH <greg@kroah.com>,
Kees Cook <keescook@google.com>,
salyzyn@android.com, kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
kernel-team@android.com, stable@vger.kernel.org,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Jeffrey Vander Stoep <jeffv@google.com>
Subject: Re: [PATCH] tracing: do not leak kernel addresses
Date: Fri, 27 Jul 2018 15:54:16 -0400 [thread overview]
Message-ID: <20180727195416.GF13922@thunk.org> (raw)
In-Reply-To: <CAG48ez1MdupASE1DMt0OWXv+rqZO-2GAbfDthEQcvNXrc2pTsQ@mail.gmail.com>
More generally, stupid question, but does Android *really* need to
have debugfs mounted? And if so, can we figure out what facilities
that are needed and can we find some other way of meeting those
requirements?
- Ted
next prev parent reply other threads:[~2018-07-27 19:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 20:22 [PATCH] tracing: do not leak kernel addresses Mark Salyzyn
2018-07-25 21:14 ` Nick Desaulniers
2018-07-26 1:07 ` Steven Rostedt
2018-07-26 15:14 ` Mark Salyzyn
2018-07-26 15:22 ` Steven Rostedt
2018-07-26 16:32 ` Nick Desaulniers
2018-07-26 16:37 ` Steven Rostedt
2018-07-26 16:59 ` Nick Desaulniers
2018-07-26 16:59 ` Nick Desaulniers
2018-07-26 21:56 ` Nick Desaulniers
2018-07-26 15:31 ` Greg KH
2018-07-26 16:52 ` Nick Desaulniers
2018-07-26 22:15 ` Steven Rostedt
2018-07-27 12:07 ` Jordan Glover
2018-07-27 13:40 ` Jann Horn
2018-07-27 13:47 ` Steven Rostedt
2018-07-27 18:13 ` Nick Desaulniers
2018-07-27 18:13 ` Nick Desaulniers
2018-07-27 18:31 ` Steven Rostedt
2018-07-27 18:41 ` Mark Salyzyn
2018-07-27 18:47 ` Jann Horn
2018-07-27 18:58 ` Jann Horn
2018-07-27 19:54 ` Theodore Y. Ts'o [this message]
2018-07-27 20:11 ` Steven Rostedt
2018-07-27 20:21 ` Theodore Y. Ts'o
2018-07-27 20:53 ` Steven Rostedt
2018-07-27 22:05 ` Sandeep Patil
2018-07-28 0:04 ` Theodore Y. Ts'o
2018-07-30 14:35 ` Sandeep Patil
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=20180727195416.GF13922@thunk.org \
--to=tytso@mit.edu \
--cc=Golden_Miller83@protonmail.ch \
--cc=greg@kroah.com \
--cc=jannh@google.com \
--cc=jeffv@google.com \
--cc=keescook@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=salyzyn@android.com \
--cc=salyzyn@google.com \
--cc=stable@vger.kernel.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.