Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the
following link:
https://bugzilla.lustre.org/show_bug.cgi?id=10796
What |Removed |Added
----------------------------------------------------------------------------
Attachment #9159|review?([EMAIL PROTECTED])|review-
Flag| |
(From update of attachment 9159)
You need to unhash newly added dentries, so that they could not be found and
are forced to be revalidated from servers the hard way. Leaving dentries in
cache with no lock would lead to problems where another client renames the
object, and then on original client you do stat on renamed name, and then on
original name and both come true, because original name has dentry hashed and
d_revalidate_it for this dentry will return true as we have locks on it
already.
_______________________________________________
Lustre-devel mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-devel
