c4d4f4147d
Use this instead of DEBUG_LASTREQS to decide whether to log lock requests. MFS: vinumlock: Catch a potential race condition where one process is waiting for a lock, and between the time it is woken and it retries the lock, another process gets it and places it in the first entry in the table. This problem has not been observed, but it's possible, and it's easy enough to fix. Submitted by: tegge vinumunlock: Catch a real bug capable of hanging a system. When releasing a lock, vinumunlock() called wakeup_one. This caused wakeups to sometimes get lost. After due consideration, we think that this is due to the fact that you can't guarantee that some other process is also waiting on the same address. This makes wakeup_one a very dangerous function to use. |
||
---|---|---|
.. | ||
COPYRIGHT | ||
makestatetext | ||
request.h | ||
statetexts.h | ||
vinum.c | ||
vinumconfig.c | ||
vinumdaemon.c | ||
vinumext.h | ||
vinumhdr.h | ||
vinuminterrupt.c | ||
vinumio.c | ||
vinumio.h | ||
vinumioctl.c | ||
vinumkw.h | ||
vinumlock.c | ||
vinummemory.c | ||
vinumobj.h | ||
vinumparser.c | ||
vinumraid5.c | ||
vinumrequest.c | ||
vinumrevive.c | ||
vinumstate.c | ||
vinumstate.h | ||
vinumutil.c | ||
vinumvar.h |