[lkml]   [2012]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC PATCH 0/3] move the secure_computing call
    On Thu, May 24, 2012 at 9:13 AM, H. Peter Anvin <> wrote:
    > I think this really screws with using seccomp for self-interception.  I
    > wouldn't inherently be opposed to the following flow:
    >        seccomp -> ptrace -> seccomp
    > ... i.e. if ptrace is enabled and we enable something, run it through
    > seccomp again, but there are bunch of use cases (mostly involving
    > SIGSYS) where doing ptrace before seccomp is just bizarre.

    Are you sure? This is ptrace syscall tracing going first.
    If seccomp generates a SIGSYS, then ptrace will still get its opportunity
    to intercept the signal and change the register state however it likes.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2012-05-24 21:02    [W:0.057 / U:1.568 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site