atom feed31 messages in org.kernel.vger.linux-kernelRe: [PATCH 2/2] x86-64: seccomp: fix ...
FromSent OnAttachments
Roland McGrathFeb 27, 2009 7:02 pm 
Roland McGrathFeb 27, 2009 7:03 pm 
Roland McGrathFeb 27, 2009 7:03 pm 
Linus TorvaldsFeb 27, 2009 7:36 pm 
Linus TorvaldsFeb 27, 2009 7:51 pm 
Ingo MolnarFeb 27, 2009 8:45 pm 
Roland McGrathFeb 27, 2009 11:25 pm 
Ingo MolnarFeb 27, 2009 11:31 pm 
Roland McGrathFeb 27, 2009 11:35 pm 
Linus TorvaldsFeb 28, 2009 9:23 am 
Greg KHFeb 28, 2009 9:45 am 
Arjan van de VenFeb 28, 2009 9:53 am 
Greg KHFeb 28, 2009 10:22 am 
Greg KHFeb 28, 2009 12:26 pm 
Benjamin HerrenschmidtFeb 28, 2009 1:09 pm 
Roland McGrathMar 1, 2009 5:44 pm 
Markus Gutschke (顧孟勤)May 6, 2009 11:46 am 
Ingo MolnarMay 6, 2009 2:28 pm 
Markus Gutschke (顧孟勤)May 6, 2009 2:45 pm 
Ingo MolnarMay 6, 2009 2:54 pm 
Markus Gutschke (顧孟勤)May 6, 2009 3:08 pm 
Ingo MolnarMay 6, 2009 3:12 pm 
Markus Gutschke (顧孟勤)May 6, 2009 3:21 pm 
Nicholas MiellMay 6, 2009 9:23 pm 
Roland McGrathMay 7, 2009 12:30 am 
Markus Gutschke (顧孟勤)May 7, 2009 1:00 am 
Ingo MolnarMay 7, 2009 3:11 am 
David WagnerMay 7, 2009 6:58 pm 
Andi KleenMay 8, 2009 12:18 pm 
Pavel MachekMay 9, 2009 10:36 pm 
Pavel MachekMay 9, 2009 10:36 pm 
Subject:Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole
From:Markus Gutschke (顧孟勤) (mar@google.com)
Date:May 6, 2009 11:46:01 am
List:org.kernel.vger.linux-kernel

On Sat, Feb 28, 2009 at 10:23, Linus Torvalds <torv@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