thread-safety of rtems_cpu_usage_report

[Till Straumann]

I look at rtems_cpu_usage_report() and it
seems to me that the code merrily scans
the _Objects_Information_table and accesses
the Thread_Control blocks it finds there
w/o using any kind of protection.

What happens, e.g., if the _Objects_Information_table
gets extended or otherwise modified by another
thread while the code is scanning the table?

Am I missing something?

-- Till