linux-kernel - [PATCH] remove EXPORT_SYMBOL for bio_integrity_init

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

Message-Id: <20080728143627.2191badd.yoichi_yuasa@tripeaks.co.jp>
Date:	Mon, 28 Jul 2008 14:36:27 +0900
From:	Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	yoichi_yuasa@...peaks.co.jp,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: [PATCH] remove EXPORT_SYMBOL for bio_integrity_init_slab()

I got section mismatch message about bio_integrity_init_slab().

WARNING: fs/built-in.o(__ksymtab+0xb60): Section mismatch in reference from the variable __ksymtab_bio_integrity_init_slab to the function .init.text:bio_integrity_init_slab()
The symbol bio_integrity_init_slab is exported and annotated __init
Fix this by removing the __init annotation of bio_integrity_init_slab or drop the export.

It only call from init_bio().
EXPORT_SYMBOL() can be removed.

Signed-off-by: Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>

diff -pruN -X /home/yuasa/Memo/dontdiff linux-orig/fs/bio-integrity.c linux/fs/bio-integrity.c
--- linux-orig/fs/bio-integrity.c	2008-07-27 20:19:06.961374681 +0900
+++ linux/fs/bio-integrity.c	2008-07-27 20:52:47.964545089 +0900
@@ -705,7 +705,6 @@ void __init bio_integrity_init_slab(void
 	bio_integrity_slab = KMEM_CACHE(bio_integrity_payload,
 					SLAB_HWCACHE_ALIGN|SLAB_PANIC);
 }
-EXPORT_SYMBOL(bio_integrity_init_slab);
 
 static int __init integrity_init(void)
 {
--
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/