Description of problem: For created files, it is not required to check permission again, this can be bypassed by paremeter caller_perm_check passed from open2_by_name but glustefs_open2() was not setting properly Version-Release number of selected component (if applicable): mainline How reproducible: always Steps to Reproduce: Run ftruncate/00.t from posix_testsuite (pjd_fstest) fails for case no 24 Actual results: test case failed Expected results: test case should pass Additional info:
Patch posted upstream https://review.gerrithub.io/#/c/361566/ for review
Verified this bug on- # rpm -qa | grep ganesha nfs-ganesha-gluster-2.4.4-8.el7rhgs.x86_64 nfs-ganesha-debuginfo-2.4.4-8.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-27.el7rhgs.x86_64 nfs-ganesha-2.4.4-8.el7rhgs.x86_64 V3 /home/new_posix/ntfs-3g-pjd-fstest/tests/chown/09.t ...... ok /home/new_posix/ntfs-3g-pjd-fstest/tests/chown/10.t ...... ok /home/new_posix/ntfs-3g-pjd-fstest/tests/ftruncate/00.t .. ok /home/new_posix/ntfs-3g-pjd-fstest/tests/ftruncate/13.t .. ok V4 home/new_posix/ntfs-3g-pjd-fstest/tests/chown/09.t ...... ok /home/new_posix/ntfs-3g-pjd-fstest/tests/chown/10.t ...... ok /home/new_posix/ntfs-3g-pjd-fstest/tests/ftruncate/00.t .. ok /home/new_posix/ntfs-3g-pjd-fstest/tests/ftruncate/13.t .. ok As no more failure of ftruncate/00.t from posix_testsuite are being observed,hence moving this bug to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2779