[go: up one dir, main page]

|
|
Log in / Subscribe / Register

New system calls: pidfd_open() and close_range()

New system calls: pidfd_open() and close_range()

Posted May 24, 2019 8:34 UTC (Fri) by Sesse (subscriber, #53779)
Parent article: New system calls: pidfd_open() and close_range()

How will error handling work? You're supposed to check the return value from close(), but if it fails, how do you know which fd had an issue…?


to post comments

New system calls: pidfd_open() and close_range()

Posted May 25, 2019 14:52 UTC (Sat) by mathstuf (subscriber, #69389) [Link]

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).


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds