Operating Systems - Semaphore vs Mutex - When to Use Which
Trace the sequence of events when a thread attempts to release a mutex it does not own. What happens internally?
Trace the sequence of events when a thread attempts to release a mutex it does not own. What happens internally?
easy🧠🧾 Concept Trace Q12 of Q15
Step-by-Step Solution
Step 1: Recall mutex ownership semantics
Mutex enforces ownership; only the thread that locked it can unlock it.Step 2: Attempt to release by non-owner
When a non-owner thread tries to release, the system detects violation.Step 3: System response
Typically, an error or exception is raised to prevent undefined behavior.Step 4: Why other options fail
The mutex is released successfully, allowing other threads to acquire it ignores ownership rules; C allows silent failure risking deadlock; B incorrectly transfers ownership.Final Answer:
Option B -> Option BQuick Check:
Mutex ownership is strict; releasing by non-owner triggers error.
Quick Trick: Mutex release must be by owner; else error occurs.
Common Mistakes:
MISTAKES- Assuming mutex releases silently even if non-owner calls unlock
- Believing ownership transfers automatically on release
- Thinking mutex behaves like a semaphore without ownership
Trap Explanation:
PITFALL- Candidates often confuse mutex with semaphore behavior, assuming release is always allowed. The strict ownership rule is a common stumbling block.
Interviewer Note:
CONTEXT- Tests understanding of mutex ownership and error handling on misuse.
Master "Semaphore vs Mutex - When to Use Which" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes