linux-kernel - Re: 2.6.25-rc7-git2: Reported regressions from 2.6.24

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: <1206704661.8514.627.camel@twins>
Date:	Fri, 28 Mar 2008 12:44:20 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Natalie Protasevich <protasnb@...il.com>
Subject: Re: 2.6.25-rc7-git2: Reported regressions from 2.6.24

On Fri, 2008-03-28 at 13:13 +0200, Adrian Bunk wrote:
> On Fri, Mar 28, 2008 at 12:00:25PM +0100, Peter Zijlstra wrote:
> > On Fri, 2008-03-28 at 11:58 +0100, Thomas Gleixner wrote:
> > > On Fri, 28 Mar 2008, Thomas Gleixner wrote:
> > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=9969
> > > > > Subject		: 2.6.24-git15 Keyboard Issue?
> > > > > Submitter	: Chris Holvenstot <cholvenstot@...cast.net>
> > > > > Date		: 2008-02-06 14:02 (51 days old)
> > > > > References	: http://lkml.org/lkml/2008/2/6/100
> > > > > 		  http://lkml.org/lkml/2008/2/13/82
> > > > > Handled-By	: Thomas Gleixner <tglx@...utronix.de>
> > > > > Patch		: http://lkml.org/lkml/2008/2/15/343
> > > >  
> > > > asked the bug reporter for an update.
> > > 
> > > Now that lkml.org is working again, I checked the patch which is
> > > referenced above and I have a hard time to connect it even remotely to
> > > that bug.
> > > 
> > > As far as I can tell the discussion on lkml identified GROUP_SCHED=y
> > > as the culprit, but I have no idea whether there was any resolution
> > > other than disabling GROUP_SCHED.
> > > 
> > > Peter ??
> > 
> > Correct, I am working on the issue but that's not going to be .25 stuff.
> 
> How are we going to get 2.6.25 working no worse than 2.6.24?
> 
> Letting GROUP_SCHED depend on BROKEN would sound logical, but that would 
> also kill FAIR_GROUP_SCHED.

Are we actually worse off than .24?

I thought group scheduling has been performing less than expected ever
since it got merged.

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