Disable LK_CANRECURSE on buffer locks. The recusion is needed only for
certain uses of snapshots and currently appears to be causing some other problems. So for now, I am reverting to the old semantics until I have had time to investigate what is causing the other problems.
This commit is contained in:
parent
b86877bef0
commit
5f9237207a
@ -237,7 +237,7 @@ extern char *buf_wmesg; /* Default buffer lock message */
|
||||
* Initialize a lock.
|
||||
*/
|
||||
#define BUF_LOCKINIT(bp) \
|
||||
lockinit(&(bp)->b_lock, PRIBIO + 4, buf_wmesg, 0, LK_CANRECURSE)
|
||||
lockinit(&(bp)->b_lock, PRIBIO + 4, buf_wmesg, 0, 0)
|
||||
/*
|
||||
*
|
||||
* Get a lock sleeping non-interruptably until it becomes available.
|
||||
|
Loading…
Reference in New Issue
Block a user