https://bugzilla.redhat.com/show_bug.cgi?id=1271065
Bug ID: 1271065
Summary: [RFE] Render all mounts of a volume defunct upon
access revocation
Product: GlusterFS
Version: 3.7.6
Component: core
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: prasanna.kalever at redhat.com
CC: bugs at gluster.org, csaba at redhat.com,
gluster-bugs at redhat.com, pkarampu at redhat.com,
prasanna.kalever at redhat.com, rcyriac at redhat.com,
rgowdapp at redhat.com, vagarwal at redhat.com
Depends On: 1245380
Blocks: 1265571
+++ This bug was initially created as a clone of Bug #1245380 +++
The auth.ssl-allow volume option -- and most likely, auth.allow as well,
although we haven't yet confirmed that -- operates along the access logic of
files in Unix: that is , one who once got a handle to a file through
successfully opening it, can happily use that handle to do I/O on the file, no
matter how the permission of the file changes later. So in our case, once one
has mounted the volume, she'll have a functional mount no matter if her accces
to the volume is revoked in the meantime.
However, the cloud industry consensual behavior is the opposite: if access is
revoked, that should take effect immediately, and further on all syscalls done
against existing mounts should fail (preferably with EACCESS) if they reach the
GlusterFS server (ie. not served from local buffer cache).
The new behavior could either be optional (along the old one) or take over
exclusively.
--- Additional comment from Prasanna Kumar Kalever on 2015-09-24 08:32:02 EDT
---
http://review.gluster.org/#/c/12229/
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1245380
[Bug 1245380] [RFE] Render all mounts of a volume defunct upon access
revocation
https://bugzilla.redhat.com/show_bug.cgi?id=1265571
[Bug 1265571] [RFE] Render all mounts of a volume defunct upon access
revocation
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.