| commit | 537632e0a54a5355cdd0330911d18c3b773f9cf7 | [log] [tgz] |
|---|---|---|
| author | Boaz Harrosh <bharrosh@panasas.com> | Wed Jul 11 15:27:13 2012 +0300 |
| committer | Boaz Harrosh <bharrosh@panasas.com> | Fri Jul 20 11:49:25 2012 +0300 |
| tree | 7b4440d84c4dffa50c81a0c8bbb86f8da93748ca | |
| parent | 62b62ad873f2accad9222a4d7ffbe1e93f6714c1 [diff] |
ore: Unlock r4w pages in exact reverse order of locking The read-4-write pages are locked in address ascending order. But where unlocked in a way easiest for coding. Fix that, locks should be released in opposite order of locking, .i.e descending address order. I have not hit this dead-lock. It was found by inspecting the dbug print-outs. I suspect there is an higher lock at caller that protects us, but fix it regardless. Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>