SIGKILL

Dave Hylands dhylands at gmail.com
Fri Jan 20 02:02:21 EST 2012


Hi Darshan,

Replying to all this time....

On Thu, Jan 19, 2012 at 9:41 PM, Darshan Ghumare
<darshan.ghumare at gmail.com> wrote:
...snip...
> What if,
> spin_lock_irqsave(&lock, flags);
> for ( ; ; )
> {
>        ;
> }
> spin_lock_irqrestore(&lock, flags);

Since you're using spinlocks and disabling interrupts, this would be
running in kernel space.

On a single core machine - you'll have locked up your entire computer.

On a multi-core machine you'll have locked up one core.

You don't need to use the spinlock, just disabling interrupts is
sufficient. Even on a multicore machine, the spinlocks would just
prevent a second core from executing the code if it tried to acquire
the same spinlock.

I don't think that there is any convenient way to kill such a thread.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com



More information about the Kernelnewbies mailing list