public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Daniel Walker <dwalker@fifo99.com>
Cc: "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 11:20:17 -0700	[thread overview]
Message-ID: <4F74A7E1.3010500@am.sony.com> (raw)
In-Reply-To: <20120329175209.GE16476@fifo99.com>

On 3/29/2012 10:52 AM, Daniel Walker wrote:
> On Thu, Mar 29, 2012 at 09:25:26AM -0700, Tim Bird wrote:
>> At the moment, I'm not considering an alternative for logger that runs
>> completely in user-space.  Having said that, this test is certainly interesting,
>> and may provide some performance numbers for logger or alternatives that would
>> be useful to compare.
>
> I was just thinking what does an accurate PID actually get you? If you
> looking at some logs with a PID of 20048, does that mean something to
> you? It doesn't actually mean much because you can't map that back to
> anything. If you have the device, and the process is still running then
> you could look it up ..
>
> So lets say logger was modified to record comm values.. That way you
> could record the actual process name AND the pid. Well if you use
> prctl(PR_SET_NAME), you can forge comm values. So that doesn't get you
> much either..
>
> So even if you record accurate PID values, it doesn't mean anything
> anyway.
Putting bogus pids in the log would allow a log DDOS-er to hide their
activity more easily.  But with the log in user-space, there are much more
insidious things that could be done to hide or corrupt log activity.  So
the sensitivity of this particular piece of log data is not that great.
  -- Tim



  reply	other threads:[~2012-03-29 18:20 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 [this message]
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

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=4F74A7E1.3010500@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=dwalker@fifo99.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox