Unsafe State and Safe State

operating-system thread-safety system unsafe bankers-algorithm
Becca Bohem picture Becca Bohem · Apr 12, 2016 · Viewed 8.8k times · Source

I have learned a little about Unsafe State and Safe State.

Safe State is when there is no chance of deadlock occuring, while unsafe state doesn't mean a deadlock has occurred yet, but means that a deadlock could happen.

What I'm trying to figure out is if a system is in an UNSAFE state, can it ever return to a safe state?

Thanks for your time!

Answer

Waseem Adil picture Waseem Adil · Jun 5, 2016

Off course it can be figured out to change it to safe state because the deadlock has not been occurred yet. it is deadlock avoidance mechanism that when you see that deadlock is going to occur in future then there is needed some mechanism to avoid deadlock from happening. so the possibility of occurring deadlock is AVOIDED.

Related questions

How can I safely create a nested directory?

What is the most elegant way to check if the directory a file is going to be written to exists, and if not, create the directory using Python? Here is what I tried: import os file_path = "/my/directory/filename.…

Read More
What is the difference between a process and a thread?

What is the technical difference between a process and a thread? I get the feeling a word like 'process' is overused and there are also hardware and software threads. How about light-weight processes in languages like Erlang? Is there a …

Read More
Difference between binary semaphore and mutex

Is there any difference between a binary semaphore and mutex or are they essentially the same?

Read More