Actions
Bug #15892
closedglobal-init: custom run_dir might have wrong permissions when setuid/setgid is deferred
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
kmroz writes in https://github.com/ceph/ceph/pull/8702
As part of deferred setuid/setgid, we also need to chown the run_dir if specified in the config. This ensures that asok files created in a custom run_dir are ultimately owned by the correct user:group.
Updated by Nathan Cutler almost 8 years ago
master PR: https://github.com/ceph/ceph/pull/8702
Updated by Nathan Cutler almost 8 years ago
- Copied to Backport #15893: jewel: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred added
Updated by Nathan Cutler almost 8 years ago
- Status changed from Pending Backport to Duplicate
- Backport deleted (
jewel)
Updated by Nathan Cutler almost 8 years ago
- Copied to deleted (Backport #15893: jewel: global-init: custom run_dir might have wrong permissions when setuid/setgid is deferred)
Updated by Nathan Cutler almost 8 years ago
- Related to Bug #15607: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
Updated by Nathan Cutler almost 8 years ago
- Related to deleted (Bug #15607: Ownership of run dir, pid file and asok file not set when deferring permissions drop)
Updated by Nathan Cutler almost 8 years ago
- Is duplicate of Bug #15607: Ownership of run dir, pid file and asok file not set when deferring permissions drop added
Actions