linux-kernel - Re: [PATCH] sched: fix to use invalid sched

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] [day] [month] [year] [list]

Message-ID: <20070920071730.GB29903@elte.hu>
Date:	Thu, 20 Sep 2007 09:17:30 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
Cc:	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: fix to use invalid sched_class


* Hiroshi Shimamoto <h-shimamoto@...jp.nec.com> wrote:

> Dmitry Adamushko wrote:
> >>> Hi Ingo,
> >>>
> >>> I found an issue about the scheduler.
> >>> If you need a test case, please let me know.
> >>> Here is a patch.
> >>> [ ... ]
> >>> The new thread should be valid scheduler class before queuing.
> >>> This patch fixes to set the suitable scheduler class.
> >> Nice fix! It's a 2.6.23 must-have fix - i'll push it out into the 
> >> scheduler tree. Thanks!
> > 
> > I think, the following approach would be a bit more appropriate
> > (the missing addition to the already existing "don't leak PI boosting prio"):
> > 
> > (not tested)
> > 
> Thank you for reviewing my patch.
> Yes, your approach looks better than mine.
> I've tested it and it looks working fine in my test case.
> I attached the test case.
> 
> Will you write a patch to replace mine?

thanks for testing it - we can queue Dmitry's clean-up for v2.6.24 
(please send me a patch for v2.6.23-rc7). The most important step was to 
get your fix into v2.6.23.

	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/