[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110107195822.39DA440467@magilla.sf.frob.com>
Date: Fri, 7 Jan 2011 11:58:22 -0800 (PST)
From: Roland McGrath <roland@...hat.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Dario Faggioli <raistlin@...ux.it>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel <linux-kernel@...r.kernel.org>,
torbenh <torbenh@....de>, john.stultz@...aro.org,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] Read THREAD_CPUTIME clock from other processes.
> Well, ptrace_may_access() protects only get_wchan/eip/esp, but
> not utime/stime.
Oh, sorry. I misread the code. As I said, I leave it to the security
folks to decide what the appropriate constraints are. All the mechanisms
for accessing the same information should just be consistent. So perhaps
this is indeed fine.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists