K 10
svn:author
V 7
attilio
K 8
svn:date
V 27
2009-10-03T15:02:55.009139Z
K 7
svn:log
V 210
When releasing a lockmgr held in shared way we need to use a write memory
barrier in order to avoid, on architectures which doesn't have strong
ordered writes, CPU instructions reordering.

Diagnosed by:	fabio

END