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

From: Andi Kleen <[email-masked]>
Date: Fri, 08 May 2009 21:18:44 +0200

"Markus Gutschke (ÜÒÐ)" <[email-masked]> writes:
>
> There are a large number of system calls that "normal" C/C++ code uses
> quite frequently, and that are not security sensitive. A typical
> example would be gettimeofday().

At least on x86-64 gettimeofday() (and time(2)) work inside seccomp because 
they're vsyscalls that run in ring 3 only.

-Andi

-- 
[email-masked] -- Speaking for myself only.