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:	Mon, 15 Jun 2015 18:19:22 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Jeremiah Mahler <jmmahler@...il.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] crypto: aesni-intel: fix crypto_fpu_exit() section
 mismatch

On Fri, Jun 12, 2015 at 09:56:40PM -0700, Jeremiah Mahler wrote:
> The '__init aesni_init()' function calls the '__exit crypto_fpu_exit()'
> function directly.  Since they are in different sections, this generates
> a warning.
> 
>   make CONFIG_DEBUG_SECTION_MISMATCH=y
>   ...
>   WARNING: arch/x86/crypto/aesni-intel.o(.init.text+0x12b): Section
>   mismatch in reference from the function init_module() to the function
>   .exit.text:crypto_fpu_exit()
>   The function __init init_module() references
>   a function __exit crypto_fpu_exit().
>   This is often seen when error handling in the init function
>   uses functionality in the exit path.
>   The fix is often to remove the __exit annotation of
>   crypto_fpu_exit() so it may be used outside an exit section.
> 
> Fix the warning by removing the __exit annotation.
> 
> Signed-off-by: Jeremiah Mahler <jmmahler@...il.com>

Applied.
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ