We have an issue where an unexport races with the lru_run_lane trying to
close a file that happens to belong to the export.

I have a patch in progress that switches first_export to first_export_id so
lru_run_lane and mdcache_lru_clean can use a valid export for the object,
and if there is none, assume unexport is closing the file.

However, I'm not sure we might not still have race issues with unexport.

Unexport cleans up the fsal export immediately, but there could be other
threads that are using the export in which case, there could be FSAL calls
after the export has been cleaned up, and in fact, we could re-open the file
in the process...

I'm not quite sure how to close all the doors here...

Frank


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Reply via email to