[lkml]   [2012]   [Feb]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v8 3/8] seccomp: add system call filtering using BPF
    On Thu, Feb 16, 2012 at 13:17, H. Peter Anvin <> wrote:
    > The other thing that you really need in addition to system call number is
    > ABI identifier, since a syscall number may mean different things for
    > different entry points.  For example, on x86-64 system call number 4 is
    > write() if called via int $0x80 but stat() if called via syscall64. This is
    > a local property of the system call, not a global per process.

    I think, the documentation said that as soon as prctl() is used to set
    a bpf filter for system calls, it automatically disallows system calls
    using an entry point other than the one used by this particular

    I was trying to come up with scenarios where this particular approach
    causes problem, but I can't think of any off the top of my head. So,
    it might actually turn out to be a very elegant way to reduce the
    attack surface of the kernel. If we are really worried about userspace
    compatibility, we could make the kernel send a signal instead of
    terminating the program, if the wrong entry point was used; not sure
    if that is needed, though.

    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-02-16 22:31    [W:0.022 / U:158.604 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site