linux-kernel - Re: Crashes during boot on 2.6.30 / 2.6.31-rc, random programs

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: <20090630091640.GB5873@cr0.nay.redhat.com>
Date:	Tue, 30 Jun 2009 17:16:40 +0800
From:	Amerigo Wang <xiyou.wangcong@...il.com>
To:	Joao Correia <joaomiguelcorreia@...il.com>
Cc:	Amerigo Wang <xiyou.wangcong@...il.com>,
	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl
Subject: Re: Crashes during boot on 2.6.30 / 2.6.31-rc, random programs

On Mon, Jun 29, 2009 at 11:30:41AM +0100, Joao Correia wrote:
>Hello
>
>The system seemed to happily ignore all the sysctl.conf changes and
>all echo VALUE >  /proc/sys/kernel/max_lock_depth


Ouch, mistake! max_lock_depth is for rt_mutex... :)

>
>So i dug a little on the source and changed
>
>include/linux/sched.h
>
># define MAX_LOCK_DEPTH 48UL
>
>to
>
># define MAX_LOCK_DEPTH 96UL
>
>and im getting no more errors. Of course, now its probably radioactive
>and about to blow up, but at least it's not complaining anymore :).

Yeah, this is right.

Let's Cc: Peter to see if he would like to change this number...

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