* Andrew Morton <[email protected]> wrote:
> If so, it's a bit sad to switch to semaphore just because of some
> errant debugging code. Perhaps it would be better to create a new
> mutex_unlock_stfu() which suppresses the warning?
the code was not using semaphores as a pure mutex thing. For example
unlocking by non-owner is not legal. AFAICS the code returns to
userspace with a held in-kernel mutex. That makes it hard for the kernel
to determine for example whether the lock has been 'forgotten', or kept
like that intentionally. Alasdair, what is the motivation for doing it
like that?
Ingo
-
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]
