linux-kernel - Re: Commit 1e5a74059f9 broke utime measurement of ptraced() 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:	Sat, 24 Dec 2011 08:42:46 +0100
From:	Mike Galbraith <efault@....de>
To:	Артем Анисимов 
	<aanisimov@...ox.ru>
Cc:	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl, mingo@...e.hu
Subject: Re: Commit 1e5a74059f9 broke utime measurement of ptraced()
 processes

On Sat, 2011-12-24 at 10:26 +0300, Артем Анисимов wrote:

>   I believe that the described behaviour is erroneous and in order to
> > lessen the odds of it [waker] being preempted again soon
> one should not mess with utime but rather use another technique. It is also 
> interesting why the *user time* needs to be affected? It is inside the kernel 
> that the tracer process is woken up, so when
> > handing a few wakeup expense cycles to the wakee
> why not account those cycles as stime?

CPU utilization shifts with wakeup preemption, so there will be visible
effect when you change wakeup preemption in any way.

>   Also I'd like to know if there is a way to get reliable utime measurements 
> in recent kernels.

If wakeup preemption is undesirable, you could run SCHED_BATCH.

	-Mike

--
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/