If you could share the details of what you want to do differently we can
discuss the best way to accomplish that.
After the research on what it would take to eliminate sub-FSAL, it’s clear that
is here to stay, and extending the sub-FSAL API could be the best solution.
Frank
From: Sriram Patil [mailto:srir...@vmware.com]
Sent: Wednesday, February 7, 2018 7:06 AM
To: nfs-ganesha-devel@lists.sourceforge.net
Subject: [Nfs-ganesha-devel] About referrals in FSAL_VFS
Hi,
I understand that we are not supposed to extend subfsals and should move to
Stackable FSALs. But, since it is not possible in some cases (e.g.
open_by_handle is not supported by the kernel), subfsal has to stay.
Currently, the referrals decision is made by FSAL_VFS depending on a specific
set of attributes and user.fs_location xattr value. If a subfsal wants to
achieve this with some other mechanism, there is no way to do that in the
current code. So, I wanted to extend the referrals functionality in FSAL_VFS
and make it more flexible by allowing subfsal to change the behavior or not
support referrals at all.
Any thoughts?
Thanks,
Sriram
---
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
