[Bugs] [Bug 955753] NFS SETATTR call with a truncate and chmod 440 fails

[bugzilla at redhat.com]

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



--- Comment #9 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8889 committed in master by Niels de Vos
(ndevos at redhat.com) 
------
commit f2131b8c79641c1bf9e20657757bcc9a62a0625a
Author: Niels de Vos <ndevos at redhat.com>
Date:   Mon Sep 29 20:03:58 2014 +0200

    gNFS: allow truncate() from SETATTR over NFS for owner

    NFSv3 does not have a TRUNCATE procedure, instead it is part of the
    SETATTR (change the 'size' attribute). SETATTR with a new 'size'
    succeeds on other NFS-servers, even when the owner of the file does not
    have write permissions. Make Gluster/NFS behave the same way, by
    checking if the RPC/pid comes from the NFS-server, and allow truncate()
    when the file is owned by the user calling SETATTR.

    BUG: 955753
    Change-Id: I4b7cb8efe5a2032c6cd2eef6af610032f76d8b39
    Signed-off-by: Niels de Vos <ndevos at redhat.com>
    Reviewed-on: http://review.gluster.org/8889
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle at redhat.com>
    Reviewed-by: soumya k <skoduri at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LYMqgBKKNS&a=cc_unsubscribe