Bug 192071 - Conflicting description for sem_wait interrupted by signal
Summary: Conflicting description for sem_wait interrupted by signal
Status: RESOLVED CODE_FIX
Alias: None
Product: Documentation
Classification: Unclassified
Component: man-pages (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: documentation_man-pages@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-07 19:41 UTC by Fabjan Sukalia
Modified: 2017-01-23 03:16 UTC (History)
1 user (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Fabjan Sukalia 2017-01-07 19:41:24 UTC
In the manpage for sem_wait(3) in the NOTES sections says that sem_wait can be interrupted by a signal despite using the SA_RESTART flag. 

The manpage for signal(7) states the opposite, that a blocking call of sem_wait and sem_timedwait will be automatically restarted if the signal handler uses the SA_RESTART flag.
Comment 1 Michael Kerrisk 2017-01-23 03:16:38 UTC
signal(7) is correct. The text in sem-wait(3) is out of date. I removed that text.

Closing this now. Thanks for the report.

Note You need to log in before you can comment on or make changes to this bug.