Larry Finger wrote:
If a particular routine needs to lock a mutex, but it may be entered with that mutex already locked,
would the following code be SMP safe?
hold_lock = mutex_trylock()
The common way to deal with this is first to restructure your function
into two. One always acquires the lock, and the other (often written
with a "__" prefix) never acquires it. The never-acquire code does the
actual work, and the always-acquire function calls it.
You then refactor the callers so that you don't have any code paths on
which you can't predict whether or not the lock will be held.
<b
-
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]
