Kinsey Moore started a new discussion on cpukit/libage/age_verify.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1137#note_145718 > + if (_Age_Locked) return RTEMS_NOT_CONFIGURED; > + > + _Age_Data.age_bracket = (uint32_t)bracket; > + _Age_Locked = true; > + return RTEMS_SUCCESSFUL; > +} > + > +uint8_t rtems_age_get_signal(void) { > + // Verify the integrity of the age data before returning it. > + // If the guard values have been tampered with, this likely > + // indicates memory corruption or a tampering attempts. > + if (_Age_Data.lower_guard != AGE_GUARD_PATTERN || > + _Age_Data.upper_guard != AGE_GUARD_PATTERN) { > + > + rtems_fatal(RTEMS_FATAL_SOURCE_STACK_CHECKER, 0xBAD1D); > + } This seems out of place. In general, RTEMS does not perform extra checks like this outside the stack checker itself. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1137#note_145718 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
