linux-kernel - Re: [PATCH] Read THREAD_CPUTIME clock from other processes.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 07 Jan 2011 20:56:15 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Roland McGrath <roland@...hat.com>
Cc:	Oleg Nesterov <oleg@...hat.com>,
	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>
Subject: Re: [PATCH] Read THREAD_CPUTIME clock from other  processes.

On Fri, 2011-01-07 at 11:50 -0800, Roland McGrath wrote:
> I think the constraints on /proc/.../stat reflect the most considered
> judgement of the security folks.  I suspect that the lack of constraint on
> /proc/.../schedstat reflects the scheduler folks just having failed to
> consider the same issues.  IMHO all access to the equivalent kinds of
> information should have the same security constraints. 

FWIW I'm fine with adding a PTRACE_MAY_READ constraint on schedstat.
--
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/