projects / platform / adaptation / renesas_rcar / renesas_kernel.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 62b62ad) | patch
ore: Unlock r4w pages in exact reverse order of locking
authorBoaz Harrosh <bharrosh@panasas.com>
Wed, 11 Jul 2012 12:27:13 +0000 (15:27 +0300)
committerBoaz Harrosh <bharrosh@panasas.com>
Fri, 20 Jul 2012 08:49:25 +0000 (11:49 +0300)
commit537632e0a54a5355cdd0330911d18c3b773f9cf7
tree7b4440d84c4dffa50c81a0c8bbb86f8da93748catree | snapshot
parent62b62ad873f2accad9222a4d7ffbe1e93f6714c1commit | 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>
fs/exofs/ore_raid.c diff | blob | history
Domain: System / Uncategorized;