From: Daniel Walker <dwalker@fifo99.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-team@android.com" <kernel-team@android.com>
Subject: Re: [RFC] Android Logger vs. Shared Memory FIGHT!
Date: Thu, 29 Mar 2012 15:58:33 -0700 [thread overview]
Message-ID: <20120329225833.GB18865@fifo99.com> (raw)
In-Reply-To: <4F74DFDC.6060904@am.sony.com>
On Thu, Mar 29, 2012 at 03:19:08PM -0700, Tim Bird wrote:
> environment. But if it can be made harder for a bad program to
> cover it's tracks, that would be nice.
Do you think adding this extra level of security is worth adding a new
kernel interface for logging ?
Daniel
prev parent reply other threads:[~2012-03-29 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 21:06 [RFC] Android Logger vs. Shared Memory FIGHT! Daniel Walker
2012-03-28 21:10 ` Daniel Walker
2012-03-29 14:50 ` Daniel Walker
2012-03-29 16:25 ` Tim Bird
2012-03-29 17:09 ` Daniel Walker
2012-03-29 17:43 ` Tim Bird
2012-03-29 17:52 ` Daniel Walker
2012-03-29 18:20 ` Tim Bird
2012-03-29 18:30 ` Daniel Walker
2012-03-29 18:50 ` Alan Cox
2012-03-29 19:09 ` Daniel Walker
2012-03-29 22:19 ` Tim Bird
2012-03-29 22:58 ` Daniel Walker [this message]
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=20120329225833.GB18865@fifo99.com \
--to=dwalker@fifo99.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox