Bug 1444537 - Chmod of 7777 and 3777 not working
Summary: Chmod of 7777 and 3777 not working
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 3.10
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-22 02:51 UTC by tchengwee
Modified: 2018-06-20 18:24 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:24:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description tchengwee 2017-04-22 02:51:51 UTC
Description of problem:
chmod of 7777 and 3777 on fuse mounted Gluster volume not working. When use stat to check the mode, the return result is 4777 and 0777
 
Version-Release number of selected component (if applicable):
Gluster 3.10.1
Ubuntu 16.04

How reproducible:
Always

Steps to Reproduce:
1. chmod a file in fuse mounted gluster volume to 7777
2. stat the file


Actual results:
stat returns 4777

Expected results:
should return 7777

Additional info:

Comment 1 Pranith Kumar K 2017-04-24 05:34:30 UTC
This is a bug in dht it seems like. It is stripping PHASE1 flags unconditionally.

(gdb)
1212                    DHT_STRIP_PHASE1_FLAGS (&local->stbuf);
(gdb) p local->stbuf.ia_prot
$18 = {
  suid = 1 '\001',
  sgid = 1 '\001', <-------
  sticky = 1 '\001', <-------
.........
}
(gdb) n
1213                    dht_set_fixed_dir_stat (&local->postparent);
(gdb) p local->stbuf.ia_prot
$19 = {
  suid = 1 '\001',
  sgid = 0 '\000', <-------
  sticky = 0 '\000', <-------
...

This is leading to 7777-->4777

Comment 2 Nithya Balachandran 2017-04-24 06:52:33 UTC
Thanks. We will take a look.

Nithya

Comment 3 Amar Tumballi 2017-04-24 09:17:02 UTC
should https://review.gluster.org/16111 fix this?

Comment 4 Shyamsundar 2018-06-20 18:24:15 UTC
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.


Note You need to log in before you can comment on or make changes to this bug.