#4511 closed defect (fixed)

Count of postponed jobs is not set to zero for a newly created rate-monotonic period object

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 6.1
Component: rtems Version: 5
Severity: normal Keywords: qualification
Cc: Blocked By:
Blocking:

Description

rtems_rate_monotonic_get_status() returns an arbitrary number for the count of postponed jobs if it is called for a newly created period object. The count of postponed jobs should be cleared to zero at object creation.

Change History (3)

comment:1 Changed on Sep 9, 2021 at 1:07:17 PM by Sebastian Huber

Keywords: qualification added

comment:2 Changed on Sep 9, 2021 at 1:08:09 PM by Sebastian Huber <sebastian.huber@…>

Resolution: fixed
Status: assignedclosed

In 82a61af/rtems:

rtems: Initialize count of postponed jobs

The rtems_rate_monotonic_get_status() directive returns an arbitrary
number for the count of postponed jobs if it is called for a newly
created period object. Set the count of postponed jobs to zero during
object creation.

Close #4511.

comment:3 Changed on Oct 6, 2021 at 6:50:11 AM by Sebastian Huber <sebastian.huber@…>

In 38c2147/rtems:

rtems: Set postponed jobs in rate-monotonic cancel

Set the postponed jobs count to zero in rtems_rate_monotonic_cancel() so that
rtems_rate_monotonic_get_status() returns a consistent status for inactive
periods.

Update #4511.

Note: See TracTickets for help on using tickets.