[Bugs] [Bug 1405147] glusterfs (posix-acl xlator layer) checks for " write permission" instead for "file owner" during open() when writing to a file

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1405147

Raghavendra G <rgowdapp at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rgowdapp at redhat.com



--- Comment #11 from Raghavendra G <rgowdapp at redhat.com> ---
RCA from Jiffin:
================
RCA:
The issue caused because open behind is trying to reopen the fd for write
operation in ob_writev(). That open will fail because the file has permissions
444(readonly) which results the write failure. If we disable the open-behind
then it will work as expected

Following is happening wrt to ganesha for cp file1 file2
client sends open adn read call on file1
client sends open call on file2
Ganesha first creates the file using glfs_h_creat, then after it get succeed,
then ganesha opens global fd with glfs_h_open which sets open_behind_fd in
ob_open call.

client sends setattr call to set permissions to 444 -- succeed

next clients sends write request,
if ganesha uses the fd opened during then it will be succeed. But in ob_writev
it find there is an open_beind_fd, then it tries to wake the fd which
internally sends open call, it will be failed because file has only read only
permissions and hence write failed.

Don't much  know about internals of open behind. Requesting Du / Mlind to have
look and provide their input for the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.