Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

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 — at Version 2

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: Indefinite
Component: score Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description (last modified by Joel Sherrill)

The sync() implementation has some weaknesses.

  1. No protection of concurrent sync() operations.
  2. Since we have no Newlib locks, other threads must not use file operations during the sync() period.
  3. Deletion of threads during the sync() may lead to all sorts of things.

Change History (2)

comment:1 Changed on 07/22/13 at 11:58:18 by Sebastian Huber

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

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
Note: See TracTickets for help on using tickets.