[RTEMS Project] #3334: deadlock in _once()
RTEMS trac
trac at rtems.org
Mon Feb 18 06:26:41 UTC 2019
#3334: deadlock in _once()
----------------------------+------------------------------
Reporter: Stavros Passas | Owner: Sebastian Huber
Type: defect | Status: closed
Priority: normal | Milestone: 5.1
Component: posix | Version: 5
Severity: normal | Resolution: fixed
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------------
Changes (by Sebastian Huber <sebastian.huber@…>):
* status: accepted => closed
* resolution: => fixed
Comment:
In [changeset:"e4ad14cc789090290550e3aa9640e4969037e8b7/rtems"
e4ad14cc/rtems]:
{{{
#!CommitTicketReference repository="rtems"
revision="e4ad14cc789090290550e3aa9640e4969037e8b7"
score: Avoid some deadlocks in _Once()
Recursive usage of the same pthread_once_t results now in a deadlock.
Previously, an error of EINVAL was returned. This usage scenario is
invalid according to the POSIX pthread_once() specification.
Close #3334.
}}}
--
Ticket URL: <http://devel.rtems.org/ticket/3334#comment:9>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list