linux-kernel - Re: [tip:tracing/urgent] tracing: Fix too large stack usage in do_one

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: <4A8EE877.90502@linux.intel.com>
Date:	Fri, 21 Aug 2009 11:33:27 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	mingo@...hat.com, "H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	a.p.zijlstra@...llo.nl, catalin.marinas@....com,
	Jens Axboe <jens.axboe@...cle.com>, fweisbec@...il.com,
	srostedt@...hat.com, tglx@...utronix.de,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [tip:tracing/urgent] tracing: Fix too large stack usage in do_one_initcall()

Linus Torvalds wrote:
> 
> I do wonder, though. Maybe we should never have that MAX_WORK limit, and 
> instead limit the parallelism by actively trying to yield when there's too 
> much work? That bootup sequence _does_ tend to have deep callchains (with 
> all the crazy device register crud), and maybe we should actively see the 
> async work code as not just a way to speed up boot, but also as a way to 
> avoid deep callchains.

makes sense; the MAX_WORK was more a sanity check to kill out of hand recursion
than anything else...
--
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/