linux-kernel - Re: kernel 2.6.23 CFS problem?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1193389542.7701.18.camel@Homer.simpson.net>
Date:	Fri, 26 Oct 2007 11:05:42 +0200
From:	Mike Galbraith <efault@....de>
To:	"Wang, Baojun" <wangbj@....edu.cn>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kernel 2.6.23 CFS problem?

On Fri, 2007-10-26 at 15:32 +0800, Wang, Baojun wrote:

> > Perhaps he has any tasks stuck in 'D' state?  If so, SysRq-t output for
> > these would be a good thing to collect.  What leads him to suspect the
> > process scheduler, etc.  More details are needed.

> The task is S+ state, please see in the attachment tarball, SysRq-t output has 
> also been attached, I wish it would help. I doubt it's the CFS problem 
> because it's first introduced into the 2.6.23 kernel.

(yeah, but there were a truckload of other changes as well)

Looking at your data, _my_ first suspect would be the 2.6.22->2.6.23
futex changes.  I'd revert all of the changes to kernel/futex.c and
kernel/futex_compat.c, and see if the problem went away.  If it didn't,
I'd then do a full git bisect to nail it down.

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