lkml.org 
[lkml]   [2011]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Read THREAD_CPUTIME clock from other processes.
On 01/07, Roland McGrath wrote:
>
> This can certainly be enhanced, but it opens some cans of worms about the
> security question. It is probably still considered an unsafe information
> leak to let every process examine every other process's thread clocks.

Yes, I was worried about possible security issues too. But, it seems,
/proc/pid/task/tid/stat (do_task_stat) shows ->utime/stime anyway.
And /proc/schedstat shows sum_exec_runtime.

> I'll leave that judgement to security folks.

Agreed.

> As well as the information leak, it is most certainly a DoS attack vector
> to allow one process to set CPU timers an another process or its threads.

No, the suggested change doesn't go that far, afaics. It only modifies
check_clock: this affects clock_getres and clock_set (which does nothing),
and posix_cpu_clock_get: affects clock_gettime().

Oleg.



\
 
 \ /
  Last update: 2011-01-07 20:45    [W:0.168 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site