On Fri, 13 Jul 2007 19:14:56 -0500 Jerry Cooperstein <[email protected]> wrote:
> kernel/mutex.c says about mutex_unlock():
>
> * This function must not be used in interrupt context.
>
> However I have done some simple test cases that show
> it works without complaint. Now I understand that one
> shouldn't do this for good reasons. So is this a
> good coding practice rule, but something that
> could appear in sloppy or poorly designed code?
>
mutex_unlock() must be called by the process which did the mutex_lock().
Doing the mutex_unlock() from an interrupt will cause warnings when run
with debugging enabled. You should run with debugging enabled when doing
any development.
Also, mutex_unlock() takes a mutex-internal spinlock in a non-irq-safe
fashion - if the timing is right, your mutex_unlock() in IRQ context will
deadlock.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
