Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1443700
| From | John Stultz <john.stultz@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC][PATCH] proc: Relax /proc/<tid>/timerslack_ns capability requirements |
| Date | 2016-07-14 21:00 +0200 |
| Message-ID | <rUU1A-4Tq-27@gated-at.bofh.it> (permalink) |
| References | <rUU1A-4Tq-7@gated-at.bofh.it> <rUU1A-4Tq-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Jul 14, 2016 at 11:52 AM, Kees Cook <keescook@chromium.org> wrote: > On Thu, Jul 14, 2016 at 11:50 AM, John Stultz <john.stultz@linaro.org> wrote: >> >> For ABI preservation, it still allows CAP_SYS_PTRACE tasks to >> access/modify timerslack values, but I'm fine with removing >> this if others agree. > > Is anything actually using this ABI yet? (Regardless, I'm fine > allowing both caps.) Not that I'm aware of... but there may be someone somewhere. Given it landed in 4.6, I suspect its fairly safe to remove. thanks -john
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC][PATCH] proc: Relax /proc/<tid>/timerslack_ns capability requirements John Stultz <john.stultz@linaro.org> - 2016-07-14 21:00 +0200
Re: [RFC][PATCH] proc: Relax /proc/<tid>/timerslack_ns capability requirements Kees Cook <keescook@chromium.org> - 2016-07-14 21:00 +0200
Re: [RFC][PATCH] proc: Relax /proc/<tid>/timerslack_ns capability requirements John Stultz <john.stultz@linaro.org> - 2016-07-14 21:00 +0200
Re: [RFC][PATCH] proc: Relax /proc/<tid>/timerslack_ns capability requirements Nick Kralevich <nnk@google.com> - 2016-07-14 22:00 +0200
csiph-web