Problem

You are debugging firmware for a Meta Portal-class embedded device running a preemptive RTOS. A high-priority security task is responsible for validating signed updates and rotating device credentials. During stress testing, this task occasionally misses its deadline even though CPU utilization is moderate.

A trace shows the following pattern:

1. A low-priority logging task acquires a mutex protecting shared flash access.
2. A high-priority security task wakes up and blocks on that mutex.
3. A medium-priority networking task handling Messenger signaling continues to run, preventing the low-priority task from releasing the mutex promptly.

Requirements

Explain what priority inversion is in this scenario and why it is dangerous in embedded security-sensitive systems.

Then answer the following:

1. Identify the roles of the low-, medium-, and high-priority tasks in the inversion.
2. Describe how priority inheritance works and how it would change scheduling behavior here.
3. Compare priority inheritance with at least one other mitigation, such as priority ceiling, reducing lock hold time, lock-free design, or interrupt/work-queue restructuring.
4. Call out implementation pitfalls in RTOS or firmware code, including nested locks, unbounded critical sections, and misuse of mutexes inside interrupt context.
5. Briefly discuss how you would verify the fix using tracing, timing measurements, or worst-case latency tests.

What a strong answer should cover

A strong answer should clearly distinguish priority inversion from starvation and deadlock, explain the scheduler mechanics precisely, and connect the issue to real embedded consequences such as missed watchdog deadlines, delayed secure boot/update flows, or dropped control-plane events. Use the example above, but generalize to firmware running on Meta hardware where timing guarantees matter.