[lkml]   [2006]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: IA32 syscall 311 not implemented on x86_64
    On 5/21/06, Dave Jones <> wrote:
    > It's a glibc problem really.

    It's not a glibc problem really. The problem is this stupid error
    message in the kernel. We rely in many dozens of places on the kernel
    returning ENOSYS in case a syscall is not implemented and we deal with
    it appropriately. There is absolutely no justification to print these
    messages except perhaps in debug kernels. IMO the sys32_ni_syscall
    functions should just return ENOSYS unless you select a special debug
    kernel. One doesn't need the kernel to detect missing syscall
    implementations, strace can do this as well.
    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: 2006-05-21 20:38    [W:0.019 / U:7.604 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site