linux-kernel - Re: [PATCH 3/3] slab: avoid __initdata warning (may be a bogus 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: <Pine.LNX.4.64.0704010011390.23774@schroedinger.engr.sgi.com>
Date:	Sun, 1 Apr 2007 00:15:06 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Paolo 'Blaisorblade' Giarrusso <blaisorblade@...oo.it>,
	linux-kernel@...r.kernel.org,
	Christoph Lameter <clameter@...r.sgi.com>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH 3/3] slab: avoid __initdata warning (may be a bogus one)

On Sat, 31 Mar 2007, Andrew Morton wrote:

> Yes, I think this is a flase positive - we'll never touch initkmem_list3[]
> after free_initmem() because of the transitions of g_cpucache_up.

Correct.

> (In which case set_up_list3s() shoud be __init, too?)

Correct. Its only called during slab bootstrap.

> Christoph, I think you looked at this previously?

If you change set_up_list3s to __init then we have the same issue with 
setup_cpu_cache right?
-
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/