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

On Thu, Mar 29, 2012 at 11:20:17AM -0700, Tim Bird wrote:
> 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


	Bogus pids or real pids it doesn't matter you can't map the pid
back to the process.

	It's true that you can wipe the whole shared memory area if it's
in userspace, but there are ways to handle that .. Not to mention
motivation due to a massive speed up over logger. For instance each app
could log to it's own logging area, and the permissions wouldn't allow
any other app to write into that area..

	You know a DoS process could just not log anything .. There's far too
many other ways to kill the system..

Daniel

  reply	other threads:[~2012-03-29 18:31 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 [this message]
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=20120329183058.GF16476@fifo99.com \
    --to=dwalker@fifo99.com \
    --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