Re: [PATCH try #2] Return access error not ECHILD on security_task_wait failure

Not having tested it or anything, that looks good to me. Thanks, Roland - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

[PATCH try #2] Return access error not ECHILD on security_task_wait failure

From: Roland McGrath <[EMAIL PROTECTED]> wait* syscalls return -ECHILD even when an individual PID of a live child was requested explicitly, when security_task_wait denies the operation. This means that something like a broken SELinux policy can produce an unexpected failure that looks just like

[PATCH try #2] Return access error not ECHILD on security_task_wait failure

From: Roland McGrath [EMAIL PROTECTED] wait* syscalls return -ECHILD even when an individual PID of a live child was requested explicitly, when security_task_wait denies the operation. This means that something like a broken SELinux policy can produce an unexpected failure that looks just like a

Re: [PATCH try #2] Return access error not ECHILD on security_task_wait failure

Not having tested it or anything, that looks good to me. Thanks, Roland - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at