linux-kernel - Re: [PATCH] dyn_array: remove one panic

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: <20080906172950.GN4856@elte.hu>
Date:	Sat, 6 Sep 2008 19:29:50 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dyn_array: remove one panic

* Yinghai Lu <yhlu.kernel@...il.com> wrote:

> Andrew said, we don't need duplicated panic.
> because __alloc_bootmem already have that.
> 
> Signed-off-by: Yinghai Lu <yhlu.kernel@...il.com>

applied to tip/irq/sparseirq, thanks.

Maybe some design documentation would be nice too, to point out that 
most of the pain we do here is because we dont have bootmem available as 
early as we need an already instantiated dyn-array based IRQ array.

So we try this mix of an abstraction of preallocated and post-allocated 
array, with pre-bootmem and post-bootmem behavior.

	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/