The share prefix can be osf- or osf-ro depending
on whether it is a readonly share. CIFS does not
create dual shares like NFS, but can use either
prefix because of the readonly snapshot special
case. So the CIFS implementation needs to find the
share or the "other share" for access rules.
Most of the NFS code is reused for this.
Unlike NFS a regular CIFS share supports both RO
and RW users.
An CIFS osf-ro share should only allow RO users.
In this case, find the share and later validate
the access rule.
Reviewed: https:/ /review. openstack. org/261086 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=cf36c111c86 a61f454e1ab6c77 a6da06b0dcb257
Committed: https:/
Submitter: Jenkins
Branch: master
commit cf36c111c86a61f 454e1ab6c77a6da 06b0dcb257
Author: mark.sturdevant <email address hidden>
Date: Wed Dec 23 11:25:47 2015 -0800
HPE3PAR finds CIFS share with either prefix
The share prefix can be osf- or osf-ro depending
on whether it is a readonly share. CIFS does not
create dual shares like NFS, but can use either
prefix because of the readonly snapshot special
case. So the CIFS implementation needs to find the
share or the "other share" for access rules.
Most of the NFS code is reused for this.
Unlike NFS a regular CIFS share supports both RO
and RW users.
An CIFS osf-ro share should only allow RO users.
In this case, find the share and later validate
the access rule.
Change-Id: I1e7a504c276e0e 28f56a564802af1 7061fe09037
Closes-Bug: #1528936