K 10
svn:author
V 7
attilio
K 8
svn:date
V 27
2009-09-30T13:26:31.348525Z
K 7
svn:log
V 293
When releasing a read/shared lock 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
Reviewed by:	jhb
Tested by:	Giovanni Trematerra
		<giovanni dot trematerra at gmail dot com>

END