Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #474, Add timecb global mutex #475

Merged
merged 2 commits into from
May 26, 2020

Conversation

jphickey
Copy link
Contributor

Describe the contribution
Adds the mutex to protect the timer callback (timecb) resource table.

Fixes #474

Testing performed
Build and confirm all unit tests pass, CFE runs normally.

Expected behavior changes
Timer callback (timcb) resource types are mutex protected.

System(s) tested on
Ubuntu 20.04
RTEMS 4.11 on pc686 via QEMU

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

astrogeco and others added 2 commits May 13, 2020 11:49
Integration Candidate COMBINED 2020-04-29 and 2020-05-06
The mutex to protect the timer callback (timecb) resource table
was missing.
@jphickey jphickey added the CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) label May 19, 2020
@skliper
Copy link
Contributor

skliper commented May 20, 2020

Does this mean everywhere it was requesting the lock/unlock it was really just a no-op and returning error (since mut == null)?

@skliper skliper added this to the 5.1.0 milestone May 20, 2020
@skliper skliper added the bug label May 20, 2020
@jphickey
Copy link
Contributor Author

Yes, but only for the "TimeCB" object table -- which typically is only used once at startup (when still single threaded) and maybe once in SCH. So low impact as far as usage goes. Surprised that this was not noticed before....

@astrogeco
Copy link
Contributor

CCB 20200520 - APPROVED

@skliper skliper added CCB-20200520 and removed CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) labels May 20, 2020
@astrogeco astrogeco added the CCB:Approved Indicates code review and approval by community CCB label May 26, 2020
@astrogeco astrogeco changed the base branch from master to integration-candidate May 26, 2020 13:44
@astrogeco astrogeco merged commit aac3e09 into nasa:integration-candidate May 26, 2020
@jphickey jphickey deleted the fix-474-timecb-lock branch June 19, 2020 16:13
@astrogeco astrogeco removed the bug label Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCB:Approved Indicates code review and approval by community CCB
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Global lock for "timecb" objects missing
3 participants