Skip to content

interfaces: allow nice/setpriority to 0-19 values for calling process by default#2772

Merged
mvo5 merged 1 commit intocanonical:masterfrom
jdstrand:seccomp-setpriority
Feb 7, 2017
Merged

interfaces: allow nice/setpriority to 0-19 values for calling process by default#2772
mvo5 merged 1 commit intocanonical:masterfrom
jdstrand:seccomp-setpriority

Conversation

@jdstrand
Copy link
Copy Markdown

@jdstrand jdstrand commented Feb 2, 2017

  • adjust default apparmor template to use nice
  • adjust default seccomp template to use nice values from 0-19 for the calling
    process
  • adjust process-control to use renice binary and nice syscall

Note, seccomp/libseccomp#69 is a limitation in the current handling of 32bit signed syscall arguments, so we use <=19 rather than >=0. This doesn't affect this PR but is something we'll want to address for things like >=-1.

… #1580968)

- adjust default apparmor template to use nice
- adjust default seccomp template to use nice values from 0-19 for the calling
  process
- adjust process-control to use renice binary and nice syscall

Note, seccomp/libseccomp#69 is a limitation in the
current handling of 32bit signed syscall arguments, so we use <=19 rather than
>=0. This doesn't affect this PR but is something we'll want to address for
things like >=-1.
@jdstrand jdstrand changed the title interfaces: allow nice/setpriority to positive values by default interfaces: allow nice/setpriority to 0-19 values for calling process by default Feb 2, 2017
@kyrofa
Copy link
Copy Markdown
Contributor

kyrofa commented Feb 2, 2017

Thanks @jdstrand! 👍 from me anyway.

@mvo5 mvo5 merged commit 7a56186 into canonical:master Feb 7, 2017
@jdstrand jdstrand deleted the seccomp-setpriority branch February 7, 2017 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants