Skip to content

Global lock for "timecb" objects missing #474

@jphickey

Description

@jphickey

Describe the bug
The internal table mutex for the timer callback (timecb) object type is missing/not implemented. This leave a potential race condition as timer callbacks are registered.

To Reproduce
Not observed in real execution at this time - but theoretically possible if two timers are registered by two tasks at the exact same time.

Expected behavior
Should be protected.

System observed on:
Ubuntu 20.04

Additional context
The global lock table is simply missing an entry for this object type.

Reporter Info
Joseph Hickey, Vantage Systems, Inc.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions