Hi, H. Peter Anvin wrote:
> There is only one error code to return for a bad user-space buffer > pointer passed to a system call in the same address space as the > system call is executed, and that is EFAULT. Furthermore, the > low-level access routines, which catch most of the faults, return > EFAULT already. > > Signed-off-by: H. Peter Anvin <[email protected]> > Reviewed-by: Oleg Nesterov <[email protected]> > Acked-by: Roland McGrath <[email protected]> > Cc: <[email protected]> > Signed-off-by: Linus Torvalds <[email protected]> Looks good, but I'm not sure why this was cc-ed to stable@. The manpage already says EFAULT There was an attempt to read from or write to an invalid area in the parent's or child's memory, probably because the area wasn't mapped or accessible. Unfortunately, under Linux, different variations of this fault will return EIO or EFAULT more or less arbitrarily. Hints? Should I be scrambling to apply this to my local kernel? Jonathan -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
