linux-kernel - Re: [PATCH 2/2] firmware/memmap: Move kobject initialisation before kobject

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: <20080730221424.0d997fb0@kopernikus.site>
Date:	Wed, 30 Jul 2008 22:14:24 +0200
From:	Bernhard Walle <bwalle@...e.de>
To:	akpm@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
	vgoyal@...hat.com, x86@...nel.org
Subject: Re: [PATCH 2/2] firmware/memmap: Move kobject initialisation before
 kobject_add()

* Bernhard Walle <bwalle@...e.de> [2008-07-30 22:12]:
>
> Because kobject_init() call could be done from firmware_map_add_entry()
> which is called before kmalloc() can be used (we use the early bootmem allocator
> here), move that call to memmap_init() which is a late_initcall.

You can leave out that patch now since kobject_init() was adapted with
the other patch ... But I think it would still make sense to include
that one.


Bernhard
-- 
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
--
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/