Hi Kees,
On Wed, Jun 11, 2014 at 5:25 AM, Kees Cook wrote:
> This adds the new "seccomp" syscall with both an "operation" and "flags"
> parameter for future expansion. The third argument is a pointer value,
> used with the SECCOMP_SET_MODE_FILTER operation. Currently, flags must
> be 0. This is f
On Fri, Jun 13, 2014 at 2:42 PM, Andy Lutomirski wrote:
> On Fri, Jun 13, 2014 at 2:37 PM, Alexei Starovoitov wrote:
>> On Fri, Jun 13, 2014 at 2:25 PM, Andy Lutomirski wrote:
>>> On Fri, Jun 13, 2014 at 2:22 PM, Alexei Starovoitov
>>> wrote:
On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wr
On Fri, Jun 13, 2014 at 2:42 PM, Andy Lutomirski wrote:
> On Fri, Jun 13, 2014 at 2:37 PM, Alexei Starovoitov wrote:
>> On Fri, Jun 13, 2014 at 2:25 PM, Andy Lutomirski wrote:
>>> On Fri, Jun 13, 2014 at 2:22 PM, Alexei Starovoitov
>>> wrote:
On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wr
On Fri, Jun 13, 2014 at 2:22 PM, Alexei Starovoitov wrote:
> On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wrote:
>> This adds the new "seccomp" syscall with both an "operation" and "flags"
>> parameter for future expansion. The third argument is a pointer value,
>> used with the SECCOMP_SET_MODE_FI
On Fri, Jun 13, 2014 at 2:37 PM, Alexei Starovoitov wrote:
> On Fri, Jun 13, 2014 at 2:25 PM, Andy Lutomirski wrote:
>> On Fri, Jun 13, 2014 at 2:22 PM, Alexei Starovoitov
>> wrote:
>>> On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wrote:
This adds the new "seccomp" syscall with both an "ope
On Fri, Jun 13, 2014 at 2:25 PM, Andy Lutomirski wrote:
> On Fri, Jun 13, 2014 at 2:22 PM, Alexei Starovoitov wrote:
>> On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wrote:
>>> This adds the new "seccomp" syscall with both an "operation" and "flags"
>>> parameter for future expansion. The third arg
On Fri, Jun 13, 2014 at 2:22 PM, Alexei Starovoitov wrote:
> On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wrote:
>> This adds the new "seccomp" syscall with both an "operation" and "flags"
>> parameter for future expansion. The third argument is a pointer value,
>> used with the SECCOMP_SET_MODE_FI
On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wrote:
> This adds the new "seccomp" syscall with both an "operation" and "flags"
> parameter for future expansion. The third argument is a pointer value,
> used with the SECCOMP_SET_MODE_FILTER operation. Currently, flags must
> be 0. This is functionall
On Tue, Jun 10, 2014 at 8:25 PM, Kees Cook wrote:
> This adds the new "seccomp" syscall with both an "operation" and "flags"
> parameter for future expansion. The third argument is a pointer value,
> used with the SECCOMP_SET_MODE_FILTER operation. Currently, flags must
> be 0. This is functionall
This adds the new "seccomp" syscall with both an "operation" and "flags"
parameter for future expansion. The third argument is a pointer value,
used with the SECCOMP_SET_MODE_FILTER operation. Currently, flags must
be 0. This is functionally equivalent to prctl(PR_SET_SECCOMP, ...).
Signed-off-by:
10 matches
Mail list logo