cinder_s..._selinux(8)
β¨ cinder_scheduler_selinux(8) β¨
okay bestie so this is the cinder_s..._selinux page from the SELinux Policy cinder_scheduler family β like, the whole manual name is cinder_s..._selinux(8) but that's not the vibe, the vibe is cinder_scheduler and we're gonna talk about it. pull up a chair π
πΈ NAME πΈ
cinder_scheduler_selinux β the Security Enhanced Linux Policy for the cinder_scheduler processes, no cap π«Ά
π¦ DESCRIPTION π¦
Security-Enhanced Linux secures the cinder_scheduler processes via flexible mandatory access control. yes. MAC. the strict kind. she's not like other access control π
The cinder_scheduler processes execute with the cinder_scheduler_t SELinux type. you can literally check if you've got these processes running by executing the ps command with the -Z qualifier. icon behavior honestly.
for example:
ps -eZ | grep cinder_scheduler_t
go off, grep π₯
π ENTRYPOINTS π
The cinder_scheduler_t SELinux type can be entered via the cinder_scheduler_exec_t file type. that's the doorway bestie πͺβ¨
The default entrypoint paths for the cinder_scheduler_t domain are the following:
/usr/bin/cinder-scheduler
one path. one icon. periodt.
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. it's giving "everybody gets a label" π
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. the SELinux cinder_scheduler policy is very flexible, allowing users to setup their cinder_scheduler processes in as secure a method as possible. slay.
The following process types are defined for cinder_scheduler:
cinder_scheduler_t
Note:semanage permissive -a cinder_scheduler_tcan be used to make the process typecinder_scheduler_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she's off the hook but she's still being watched π
π BOOLEANS π
SELinux policy is customizable based on least access required. cinder_scheduler policy is extremely flexible and has several booleans that allow you to manipulate the policy and run cinder_scheduler with the tightest access possible. tightest access possible is the whole aesthetic πβ¨
- If you want to dontaudit all daemons scheduling requests (
setsched,sys_nice), you must turn on thedaemons_dontaudit_schedulingboolean. Enabled by default.
setsebool -P daemons_dontaudit_scheduling 1
- If you want to deny user domains applications to map a memory region as both executable and writable, this is dangerous and the executable should be reported in bugzilla, you must turn on the
deny_execmemboolean. Disabled by default.
setsebool -P deny_execmem 1
- If you want to control the ability to mmap a low area of the address space, as configured by
/proc/sys/vm/mmap_min_addr, you must turn on themmap_low_allowedboolean. Disabled by default.
setsebool -P mmap_low_allowed 1
- If you want to disable kernel module loading, you must turn on the
secure_mode_insmodboolean. Disabled by default.
setsebool -P secure_mode_insmod 1
- If you want to allow unconfined executables to make their heap memory executable. Doing this is a really bad idea. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the
selinuxuser_execheapboolean. Disabled by default.
setsebool -P selinuxuser_execheap 1
- If you want to allow unconfined executables to make their stack executable. This should never, ever be necessary. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the
selinuxuser_execstackboolean. Disabled by default.
setsebool -P selinuxuser_execstack 1
lowkey screaming at this one β heap and stack executables are a whole red flag situation, report them in bugzilla fr fr π
π MANAGED FILES π
The SELinux process type cinder_scheduler_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. (can't skip that part, bestie, DAC said what she said π
)
file_type- all files on the system
like. all files. the whole system. she's got range π
π§ FILE CONTEXTS π§
SELinux requires files to have an extended attribute to define the file type. xattr moment β¨
You can see the context of a file using the -Z option to ls.
Policy governs the access confined processes have to these files. SELinux cinder_scheduler policy is very flexible, allowing users to setup their cinder_scheduler processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the cinder_scheduler, if you wanted to store files with these types in a different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk. moving files around and keeping the labels? that's the glow-up π
semanage fcontext -a -t cinder_scheduler_exec_t '/srv/cinder_scheduler/content(/.*)?'
restorecon -R -v /srv/mycinder_scheduler_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise π
The following file types are defined for cinder_scheduler:
cinder_scheduler_exec_tβ Set files with thecinder_scheduler_exec_ttype, if you want to transition an executable to thecinder_scheduler_tdomain.cinder_scheduler_tmp_tβ Set files with thecinder_scheduler_tmp_ttype, if you want to store cinder scheduler temporary files in the/tmpdirectories. temp file energy, iconic πcinder_scheduler_unit_file_tβ Set files with thecinder_scheduler_unit_file_ttype, if you want to treat the files as cinder scheduler unit content.
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. temporary vs permanent, know the difference bestie π
π COMMANDS π
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings. yes, a GUI, for the mouse girlies π±οΈβ¨
π«Ά AUTHOR π«Ά
This manual page was auto-generated using sepolicy manpage. robot wrote her. she's still flawless π
π₯ SEE ALSO π₯
selinux(8), cinder_scheduler(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
and that's the whole page bestie, no notes π this gem came from the cinder_scheduler manual, dated 26-10-06, and it goes by cinder_s..._selinux(8) when it's being formal. mwah ππ¦πΈ
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms