From: Dave Hansen <dave@sr71.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
linux-security-module@vger.kernel.org,
linux-arch@vger.kernel.org, sfr@canb.auug.org.au,
zohar@linux.vnet.ibm.com, linux@arm.linux.org.uk,
monstr@monstr.eu, ralf@linux-mips.org, benh@kernel.crashing.org,
paulus@samba.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, lethal@linux-sh.org, x86@kernel.org,
james.l.morris@oracle.com
Subject: Re: [PATCH] kconfig: consolidate arch-specific seccomp options
Date: Thu, 30 Jan 2014 08:48:39 -0800 [thread overview]
Message-ID: <52EA8267.4020107@sr71.net> (raw)
In-Reply-To: <20140130085551.GB2024@gmail.com>
On 01/30/2014 12:55 AM, Ingo Molnar wrote:
>> > + This kernel feature is useful for number crunching applications
>> > + that may need to compute untrusted bytecode during their
>> > + execution. By using pipes or other transports made available to
> I'd change and simplify the first sentence to:
>
>> > + This kernel feature is useful to sandbox runtimes that need
>> > + to execute untrusted machine code.
> Seccomp isn't primarily about number crunching anymore, and it's
> definitely not about 'bytecode' in the classical sense either.
I'll change that if I need to send it again. Otherwise, I'll leave it
to the folks who actually know something about the feature, which isn't me.
next prev parent reply other threads:[~2014-01-30 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 19:10 [PATCH] kconfig: consolidate arch-specific seccomp options Dave Hansen
2014-01-30 8:55 ` Ingo Molnar
2014-01-30 9:15 ` Benjamin Herrenschmidt
2014-01-30 16:48 ` Dave Hansen [this message]
2014-01-31 6:58 ` Ingo Molnar
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=52EA8267.4020107@sr71.net \
--to=dave@sr71.net \
--cc=benh@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=james.l.morris@oracle.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=monstr@monstr.eu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=zohar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.