On Thu, Jul 14, 2016 at 11:52 AM, Kees Cook <[email protected]> wrote: > On Thu, Jul 14, 2016 at 11:50 AM, John Stultz <[email protected]> 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
