From: Daniel Walker <dwalker@fifo99.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tim Bird <tim.bird@am.sony.com>,
"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 12:09:23 -0700 [thread overview]
Message-ID: <20120329190922.GG16476@fifo99.com> (raw)
In-Reply-To: <20120329195007.07d53db7@pyramind.ukuu.org.uk>
On Thu, Mar 29, 2012 at 07:50:07PM +0100, Alan Cox wrote:
>
> The question is whether you are trying to record data for analysis in a
> hostile environment or you are trying to do useful debugging. If your
> apps are non hostile then PR_SET_NAME is actually useful in logging to
> split apart different executions of the same daemon.
True..
> The Android logger has no security model of any real kind so it's clearly
> about the debug side. In that case the PID lets you correlate with other
> logs, the comm data might be useful.
Your right it doesn't have much in terms of security, but Tim is suggesting
that it is a hostile environment in need of what little security it has.
If your logging on a hostile system then Android's logger and my shared
memory version are both wide open. However, that doesn't mean you could lock
both down in some way.
Daniel
next prev parent reply other threads:[~2012-03-29 19:09 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 [this message]
2012-03-29 22:19 ` Tim Bird
2012-03-29 22:58 ` Daniel Walker
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=20120329190922.GG16476@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