You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current seccomp changes completely disallow calling sched_setscheduler, but we can safely allow calling it with policy==SCHED_OTHER/BATCH/IDLE, as really the only problem is the various real-time classes.
The profile argument is the second (id 1) and the values for the classes are OTHER=0, BATCH==3, IDLE==5, so the rule should look like:
Unfortunately we can't allow this with sched_setattr, because in that syscall the profile argument is not a separate syscall argument but is stored in the memory pointed to by the attr pointer argument.
The current seccomp changes completely disallow calling sched_setscheduler, but we can safely allow calling it with policy==SCHED_OTHER/BATCH/IDLE, as really the only problem is the various real-time classes.
The profile argument is the second (id 1) and the values for the classes are OTHER=0, BATCH==3, IDLE==5, so the rule should look like:
The text was updated successfully, but these errors were encountered: