Opened on 07/19/13 at 14:13:23
Last modified on 08/13/17 at 23:50:53
#2129 new defect
sync() implementation is dangerous
Reported by: | Sebastian Huber | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Indefinite |
Component: | score | Version: | |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description (last modified by Sebastian Huber)
The sync() implementation has some weaknesses.
- No protection of concurrent sync() operations.
- Since we have no Newlib locks, other threads must not use file operations during the sync() period.
- Deletion of threads during the sync() may lead to all sorts of things.
Change History (6)
comment:1 Changed on 07/22/13 at 11:58:18 by Sebastian Huber
comment:2 Changed on 11/23/14 at 16:17:31 by Joel Sherrill
Description: | modified (diff) |
---|---|
Owner: | changed from Joel Sherrill to Sebastian Huber |
Status: | new → assigned |
comment:3 Changed on 11/24/14 at 18:58:28 by Gedare Bloom
Version: | HEAD → 4.11 |
---|
Replace Version=HEAD with Version=4.11 for the tickets with Milestone >= 4.11
comment:4 Changed on 11/28/14 at 12:07:11 by Sebastian Huber
Milestone: | 4.11 → 5.0 |
---|
I don't have time and budget to fix this at the moment.
comment:5 Changed on 02/18/15 at 14:38:35 by Sebastian Huber
Description: | modified (diff) |
---|---|
Owner: | Sebastian Huber deleted |
Status: | assigned → new |
comment:6 Changed on 08/13/17 at 23:50:53 by Chris Johns
Milestone: | 5.0 → Indefinite |
---|---|
Version: | 4.11 |
Note: See
TracTickets for help on using
tickets.
I think this is the easy part. Operations on all threads are currently questionable in general. Its also related to:
http://www.rtems.org/pipermail/rtems-devel/2013-July/003509.html