linux-kernel - Re: Interesting interaction between lguest and CFS

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]

Message-ID: <20070605071011.GA25163@elte.hu>
Date:	Tue, 5 Jun 2007 09:10:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Matt Mackall <mpm@...enic.com>, akpm@...ux-foundation.org,
	Linux-kernel@...r.kernel.org
Subject: Re: Interesting interaction between lguest and CFS


* Rusty Russell <rusty@...tcorp.com.au> wrote:

> This sounds like the waker process (nice 19) not getting a chance to 
> run.  You can hack around it for the moment by changing "nice(19)" in 
> Documentation/lguest/lguest.c to something less aggressive.

even if the waker runs at nice+19, under CFS (which schedules 
deterministically) it should not be delayed by a single nice-0 task by 
more than ~70 msecs. That is a far cry from the 'seconds' that Matt saw 
- and the sched stats he sent look anomalous too. Also, i'm not able to 
reproduce it at all - while any nice+19 related problem should be 
readily reproducable on my box too. So my current take is that this is 
some sort of host-side CFS related problem and that the lguest host 
threads somehow were the first ones that managed to trigger it in some 
really bad way.

OTOH i do agree with your patch, that nice+19 thing is quite hacky :-)

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