Bug 2006691

Summary:	pybind/mgr/volumes: first subvolume permissions set perms on /volumes and /volumes/group
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Kotresh HR <khiremat>
Component:	CephFS	Assignee:	Patrick Donnelly <pdonnell>
Status:	CLOSED DUPLICATE	QA Contact:	Hemanth Kumar <hyelloji>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3	CC:	ceph-eng-bugs, sweil, vereddy
Target Milestone:	---
Target Release:	5.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-02 01:03:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kotresh HR 2021-09-22 08:06:50 UTC

Description of problem:


Because we use the "mkdirs" method for making parents to a subvolume, the perms for the subvolume specified by --mode are used for all parents too. This is wrong because you can get:

pdonnell@vossi04 ~/ceph/build$ bin/ceph fs subvolume create a d --mode=777 --size=$((2**30))
pdonnell@vossi04 ~/mnt/tmp.0cSPBAJM59$ ls -lha volumes/
total 1.5K
drwxrwxrwx. 3 root     root      120 Jul 27 19:17 .
drwxr-xr-x. 4 pdonnell pdonnell 473M Jul 27 19:17 ..
-rwxr-xr-x. 1 root     root        0 Jul 27 19:17 _:d.meta
drwxrwxrwx. 3 root     root      120 Jul 27 19:17 _nogroup

volumes should be 0755 and _nogroup should be 0755.


Please look into the attached upstream tracker for more info

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2021-09-22 08:06:56 UTC

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 2 Patrick Donnelly 2021-11-02 01:03:05 UTC


*** This bug has been marked as a duplicate of bug 2005959 ***