[LU-377] POSIX: chmod.5: chown("chmod-t.5", 1001, 1000) failed - errno 1 (EPERM)

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 1.8.8, Lustre 1.8.7, Lustre 1.8.6
• Type: Bug
• Priority: Minor
• Reporter: Jian Yu
• Assignee: WC Triage
• Resolution: Fixed

Environment

Lustre Branch: b1_8
Lustre Build: http://newbuild.whamcloud.com/job/lustre-b1_8/61/
Distro/Arch: CentOS5.6/x86_64(OFED 1.5.3, ext4)

• Severity: 3
• Bugzilla ID: 23,360

Description

Here is the result of running the LSB-VSX POSIX test suite (lts_vsx-pcts2.0beta2.tgz):
https://maloo.whamcloud.com/test_sets/f610526e-8b52-11e0-aab9-52540025f9af

The baseline is ext4.

FAILURE DESCRIPTIONS:

####################################################
Test Name: chmod.5 Unresolved

	Test Description:
If the implementation supports the setting of S_ISUID and S_ISGID,
then a successful call to chmod(path, mode), when the effective user
ID matches the user ID of the file, sets S_ISUID, S_ISGID, and the
file permission bits of the named file according to the bit pattern
contained in the argument mode and returns a value of zero.
In FIPS, XPG4 and UNIX modes, setting of S_ISUID and S_ISGID must be
supported.
Posix Ref: Component CHMOD Assertion 5.6.4.2-27(C)

	Test Information:
deletion reason: chown("chmod-t.5", 1001, 1000) failed - errno 1 (EPERM)

Comments

[Andreas Dilger]

Does the MDS have the group_upcall configured, and /etc/passwd and /etc/group modified to match the users and groups configured on the client? Do you know if this (and other POSIX tests) passed with 1.8.5?

[Jian Yu]

Does the MDS have the group_upcall configured, and /etc/passwd and /etc/group modified to match the users and groups configured on the client?

Yes.

# lctl get_param mds.*.group_upcall
mds.lustre-MDT0000.group_upcall=/usr/sbin/l_getgroups

Do you know if this (and other POSIX tests) passed with 1.8.5?

All of the tests also failed on Lustre 1.8.4: bug 23359

It seems that the POSIX compliance testing was not run on Lustre 1.8.5.

[Jian Yu]

Lustre Branch: v1_8_6_RC2
Lustre Build: http://newbuild.whamcloud.com/job/lustre-b1_8/80/
e2fsprogs Build: http://newbuild.whamcloud.com/job/e2fsprogs-master/40/
Distro/Arch: RHEL5/x86_64(OFED 1.5.3.1, kernel version: 2.6.18-238.12.1.el5_lustre)

POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/2cd4d244-98d1-11e0-9a27-52540025f9af

The baseline is ext4.

[Jian Yu]

Lustre Tag: v1_8_7_WC1_RC1
Lustre Build: http://newbuild.whamcloud.com/job/lustre-b1_8/142/
e2fsprogs Build: http://newbuild.whamcloud.com/job/e2fsprogs-master/65/
Distro/Arch: RHEL5/x86_64(server, OFED 1.5.3.2, ext4-based ldiskfs), RHEL6/x86_64(client, in-kernel OFED)

POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/30866dc0-f3ef-11e0-908b-52540025f9af

The baseline is ext4.

[Jian Yu]

Lustre Tag: v1_8_8_WC1_RC1
Lustre Build: http://build.whamcloud.com/job/lustre-b1_8/195/
e2fsprogs Build: http://build.whamcloud.com/job/e2fsprogs-master/278/
Distro/Arch: RHEL5.8/x86_64(server, ext4-based ldiskfs), RHEL6.2/x86_64(client)
Network: IB (in-kernel OFED)

POSIX compliance testing report: https://maloo.whamcloud.com/test_sets/99712946-9b2a-11e1-a0a0-52540035b04c

The baseline is ext4.

[Andreas Dilger]

Does this test still fail with master, or should it be closed?

[Jian Yu]

posix test passed on master branch (build #3593):
https://testing.hpdd.intel.com/test_sets/ecf1cd8c-4408-11e7-b3fe-5254006e85c2

Let's close this ticket.