Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the
following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11514
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
huanghua 07/01/10 10:02:53
Modified: obdclass lu_object.c
Log:
As Nikita suggested, assertion on ls_busy in lu_site_fini() can be safely
removed:
After switching to read-write lock for lu_object hash table, lu_site->ls_busy
is no longer
strictly correct, because it is incremented under read-lock in
htable_lookup().
_______________________________________________
Lustre-devel mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-devel
