linux-kernel - Re: [git pull] scheduler fixes

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:	Tue, 4 Dec 2007 10:28:51 -0800
From:	Greg KH <greg@...ah.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Luiz Fernando N. Capitulino" <lcapitulino@...driva.com.br>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	herton@...driva.com.br, dvgevers@...all.nl
Subject: Re: [git pull] scheduler fixes

On Tue, Dec 04, 2007 at 05:18:27PM +0100, Ingo Molnar wrote:
> 
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
> > The problem is on SMP: if sched_rr_get_interval() gets a task from an 
> > otherwise idle runqueue, then rq->load.weight is 0. Normally 
> > sched_slice() is only used on a busy runqueue. So the correct fixup 
> > site is not in sched_slice() but in sys_sched_rr_get_interval() - i'm 
> > working on the right fix, i hope to be able to send a pull request in 
> > a few minutes.
> 
> the problem is on UP too - if there are no SCHED_OTHER tasks. I've 
> tested the fix and it solves the problem for various combinations of 
> crash.c. I've updated sched.git, please pull it from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched.git
> 
> It has another commit besides this fix. Thanks,

Can you make up something that I can apply for 2.6.23-stable?  or is
this not an issue on that tree?

thanks,

greg k-h
--
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/