linux-kernel - Re: [PATCH] get rid if __cpuinit and _

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

Date:	Fri, 24 Oct 2008 11:01:48 -0700
From:	"Tony Luck" <tony.luck@...il.com>
To:	"Arjan van de Ven" <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH] get rid if __cpuinit and __cpuexit

On Wed, Oct 22, 2008 at 6:07 PM, Arjan van de Ven <arjan@...radead.org> wrote:
> interesting... I don't see how that can be unless the checks originally
> had a bug and did not complain about a reference to __init(data) memory
> from inside __cpuinit memory...
> (in which case my point of this being too complex and fragile is
> proven ;-)

Definitely too complex and fragile.  I rebuilt with
CONFIG_DEBUG_SECTION_MISMATCH=y
and found that this patch just shuffled everything
around.  Only 4 mismatch warnings were the same
with this patch, 11 old warnings went away, but
14 new ones appeared!

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