From: Christopher Yeoh <cyeoh@au1.ibm.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] CMA: Do no enable it by default
Date: Wed, 6 Jun 2012 10:54:59 +0930 [thread overview]
Message-ID: <20120606105459.49430920@Gantu> (raw)
In-Reply-To: <20120605110541.GC13495@aftab.osrc.amd.com>
On Tue, 5 Jun 2012 13:05:41 +0200
Borislav Petkov <bp@amd64.org> wrote:
>
> CROSS_MEMORY_ATTACH is a MPI feature which shouldn't be enabled by
> default on every linux system simply because the majority of users do
> not need it.
btw although CMA was primarily written for MPI it is used by more than
just MPI implementations. For example, recent versions of strace now
use it instead of PTRACE_PEEKDATA if its available:
http://article.gmane.org/gmane.comp.sysutils.strace.devel/2467/match=process_vm_readv
> Besides, in the config option it says "... which allow a process with
> the correct privileges to directly read from or write to to another
> process's address space.", which, if the reading process has somehow
> gained privileges (as that never happens) is your security issue right
> there.
The privileges required are exactly the same as required to ptrace the
target. You're rather stuffed anyway if you have a hostile process with
those privileges.
Regards,
Chris
--
cyeoh@au.ibm.com
next prev parent reply other threads:[~2012-06-06 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120531153512.GK14515@aftab.osrc.amd.com>
2012-05-31 15:42 ` CROSS_MEMORY_ATTACH default y? Borislav Petkov
2012-06-01 1:06 ` Christopher Yeoh
2012-06-05 11:05 ` [PATCH] CMA: Do no enable it by default Borislav Petkov
2012-06-05 16:46 ` Linus Torvalds
2012-06-05 17:09 ` Borislav Petkov
2012-06-05 18:03 ` [PATCH -v2] " Borislav Petkov
2012-06-06 1:24 ` Christopher Yeoh [this message]
2012-06-06 12:59 ` [PATCH] " Borislav Petkov
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=20120606105459.49430920@Gantu \
--to=cyeoh@au1.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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