On Sat, 29 September 2007 13:00:11 -0700, Andrew Morton wrote:
quoted text
> 
> err, it's basically an open-coded mutex via which one thread can get
> exclusive access to some parts of an inode's internals.  Perhaps it could
> literally be replaced with a mutex.  Exactly what I_LOCK protects has not
> been documented afaik.  That would need to be reverse engineered :(

I believe you actually have some documentation in your tree.  At least
the behaviour after my I_SYNC patch has been documented with that patch.

Jörn

-- 
"Error protection by error detection and correction."
-- from a university class
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/