[Top] [All Lists]

Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole

To: Linus Torvalds <>
Subject: Re: [PATCH 2/2] x86-64: seccomp: fix 32/64 syscall hole
From: Markus Gutschke <>
Date: Wed, 6 May 2009 11:42:29 -0700
Cc: Roland McGrath <>, Andrew Morton <>,,,,,,
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; s=beta; t=1241635352; bh=xHWjgJtHuWOwFnADuUENAcK9ZhQ=; h=DomainKey-Signature:MIME-Version:Sender:In-Reply-To:References: Date:X-Google-Sender-Auth:Message-ID:Subject:From:To:Cc: Content-Type:X-System-Of-Record; b=KlWe0yI+VVsUrMtM4EMqwGkR0cDp4qs 6756rvgHlo1bsx52YLfmlafRhrQp3tnhQFXl/8J683W7nmYSY4fGWDQ==
Domainkey-signature: a=rsa-sha1; s=beta;; c=nofws; q=dns; h=mime-version:sender:in-reply-to:references:date: x-google-sender-auth:message-id:subject:from:to:cc:content-type:x-system-of-record; b=CPOUVrmzW9wHpCJDhJSb6ufIh4ePQKN/VfUdE8OuzLRbm3xLOeyiPNJfTzyUth9jE 4Pc3SxlKItSdPA6Y6i7ag==
In-reply-to: <alpine.LFD.2.00.0902280916470.3111@localhost.localdomain>
Original-recipient: rfc822;
References: <> <> <alpine.LFD.2.00.0902271932520.3111@localhost.localdomain> <alpine.LFD.2.00.0902271948570.3111@localhost.localdomain> <> <alpine.LFD.2.00.0902280916470.3111@localhost.localdomain>
On Sat, Feb 28, 2009 at 10:23, Linus Torvalds <> 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.

<Prev in Thread] Current Thread [Next in Thread>