linux-kernel - Re: slab: setup allocators earlier in the boot sequence

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>] [day] [month] [year] [list]

Date:	Fri, 12 Jun 2009 11:29:52 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	git-commits-head@...r.kernel.org
Subject: Re: slab: setup allocators earlier in the boot sequence

On Thu, 2009-06-11 at 19:59 +0000, Linux Kernel Mailing List wrote:
> Gitweb:     http://git.kernel.org/linus/83b519e8b9572c319c8e0c615ee5dd7272856090
> Commit:     83b519e8b9572c319c8e0c615ee5dd7272856090
> Parent:     c91c4773b334d4d3a6d44626dc2a558ad97b86f3
> Author:     Pekka Enberg <penberg@...helsinki.fi>
> AuthorDate: Wed Jun 10 19:40:04 2009 +0300
> Committer:  Pekka Enberg <penberg@...helsinki.fi>
> CommitDate: Thu Jun 11 19:15:56 2009 +0300
> 
>     slab: setup allocators earlier in the boot sequence
>     
>     This patch makes kmalloc() available earlier in the boot sequence so we can get
>     rid of some bootmem allocations. The bulk of the changes are due to
>     kmem_cache_init() being called with interrupts disabled which requires some
>     changes to allocator boostrap code.
>     
>     Note: 32-bit x86 does WP protect test in mem_init() so we must setup traps
>     before we call mem_init() during boot as reported by Ingo Molnar:

This seem to explode in various places on powerpc :-(

It would have been nice if we had enough advance warning to actually fix
our archs too ... I had no idea it was going to be merged that soon. I
did plan to dig into this at some stage but that was too soon. Maybe it
should have been a CONFIG option for a couple of -rc's ?

But yeah, of course, only x86 matters right ? We can break everybody
else and fuck up bisection just for fun...

Cheers,
Ben.


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