On Sun, 15 Apr 2018 13:17:27 +0530, Ivid Suvarna said: > I had tried with the module where I put a busy loop inside spinlock > but was not able to cause any lockups. Maybe this is because of SMP > which schedule the job to other CPU. "How do I make a task to run on > single CPU only?"
So you get a kernel thread that's taken a lock and will busy-loop and not free it. What sort of lockup do you expect will be detected from this? Would the results be any different if you didn't take a lock before busy-looping? For bonus points - what additional things have to happen before a livelock happens? And before a deadlock happens?
Description: PGP signature