Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 27 Jul 2018 16:11:03 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Theodore Y. Ts'o" <tytso@....edu>
Cc: Jann Horn <jannh@...gle.com>, salyzyn@...gle.com, Nick Desaulniers
 <ndesaulniers@...gle.com>, Golden_Miller83@...tonmail.ch, Greg KH
 <greg@...ah.com>, Kees Cook <keescook@...gle.com>, salyzyn@...roid.com,
 kernel list <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...hat.com>,
 kernel-team@...roid.com, stable@...r.kernel.org, Kernel Hardening
 <kernel-hardening@...ts.openwall.com>, Jeffrey Vander Stoep
 <jeffv@...gle.com>
Subject: Re: [PATCH] tracing: do not leak kernel addresses

On Fri, 27 Jul 2018 15:54:16 -0400
"Theodore Y. Ts'o" <tytso@....edu> wrote:

> 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?

I do know that they have applications that use ftrace. But then again,
the ftrace files are under its own tracefs file system (that just
happens to be mounted when debugfs is). That said, I would assume that
other Android utilities are using other debugfs files for system
status and such.

-- Steve

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ