linux-kernel - Re: [PATCH] x86: fix improper .init-type section references

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: <466FBDC1.76E4.0078.0@novell.com>
Date:	Wed, 13 Jun 2007 09:49:53 +0200
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Satyam Sharma" <satyam.sharma@...il.com>
Cc:	"Venkatesh Pallipadi" <venkatesh.pallipadi@...el.com>,
	"Sam Ravnborg" <sam@...nborg.org>, "Andi Kleen" <ak@...e.de>,
	<linux-kernel@...r.kernel.org>, <patches@...-64.org>
Subject: Re: [PATCH] x86: fix improper .init-type section references

>But then why not simply lose the __exit (and .exit.*) altogether? Because
>__exit becomes redundant in the suggested changed semantics -- just mark
>all the cleanup code as __init too (when it's built-in, the only
>callsite for the
>cleanup code would be from the startup code in .init.*, and when modular,
>__init and __exit lose all relevance anyway).

Because of the non-builtin case (__init still has significance in the modular case,
it's only __exit that doesn't). For the builtin case, __init could certainly be
identical to __exit.

Jan

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