New system calls: pidfd_open() and close_range()
New system calls: pidfd_open() and close_range()
Posted May 25, 2019 14:52 UTC (Sat) by mathstuf (subscriber, #69389)In reply to: New system calls: pidfd_open() and close_range() by Sesse
Parent article: New system calls: pidfd_open() and close_range()
There have been articles about the return value of close(2) here before. Basically the state of the descriptor after a failed close(2) is undefined, even for EINTR, so checking the return value is only of "notify that something went wrong" value. There's nothing to actually *do* in response an error from close(2).