Discussion
A task holds a mutex and is then deleted by another task. The consequence is
Answer: D
Most kernels take no interest in what a deleted task was holding, so the lock is orphaned and every future acquirer blocks for ever. This is the strongest of the several reasons that deleting tasks at run time is discouraged in embedded designs.
No comment is present. Be the first to comment.
Loading…
Post your comment
Please log in or register to post a comment.
Examination Categories
- SSC Exams
- Banking Exams
- Teaching Exams
- Civil Services Exams
- Railways Exams
- Engineering Recruitment Exams
- Defence Exams
- State Government Exams
- Police Exams
- Insurance Exams
- Nursing Exams
- Other Government Exams
- NRA CET
- PG Entrance Exams
- Campus Placement
- MBA Entrance Exams
- CUET and UG Entrance
- Judiciary Exams
- Regulatory Body Exams
- Software Development