LSM: switch to blocking policy update notifiers
Atomic policy updaters are not very useful as they cannot usually perform the policy updates on their own. Since it seems that there is no strict need for the atomicity, switch to the blocking variant. While doing so, rename the functions accordingly. Signed-off-by: Janne Karhunen <janne.karhunen@gmail.com> Acked-by: Paul Moore <paul@paul-moore.com> Acked-by: James Morris <jamorris@linux.microsoft.com> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
This commit is contained in:

committed by
Mimi Zohar

parent
9e1e5d4372
commit
42df744c41
@@ -180,7 +180,7 @@ static ssize_t sel_write_enforce(struct file *file, const char __user *buf,
|
||||
selnl_notify_setenforce(new_value);
|
||||
selinux_status_update_setenforce(state, new_value);
|
||||
if (!new_value)
|
||||
call_lsm_notifier(LSM_POLICY_CHANGE, NULL);
|
||||
call_blocking_lsm_notifier(LSM_POLICY_CHANGE, NULL);
|
||||
}
|
||||
length = count;
|
||||
out:
|
||||
|
Reference in New Issue
Block a user