[proxy] web.archive.org — ← back | site home | direct (HTTPS) ↗ | proxy home | ◑ dark◐ light
Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
Weaver
FAQ
 
From: Markus Gutschke (顧孟勤 <markus <at> google.com>
Subject: Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole
Newsgroups: gmane.linux.ports.sparc, gmane.linux.kernel, gmane.linux.ports.mips.general, gmane.linux.ports.ppc64.devel
Date: 2009-05-06 18:46:24 GMT (4 years, 7 weeks, 1 hour and 22 minutes ago)
On Sat, Feb 28, 2009 at 10:23, Linus Torvalds
<torvalds <at> linux-foundation.org> wrote:
> And I guess the seccomp interaction means that this is potentially a
> 2.6.29 thing. Not that I know whether anybody actually _uses_ seccomp. It
> does seem to be enabled in at least Fedora kernels, but it might not be
> used anywhere.

In the Linux version of Google Chrome, we are currently working on
code that will use seccomp for parts of our sandboxing solution.

Markus
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html