linux-kernel - OSS sound core optionalization has __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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0809120822n40c8f99k45bb91e670cca805@mail.gmail.com>
Date:	Fri, 12 Sep 2008 11:22:21 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	tj@...nel.org
Cc:	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: OSS sound core optionalization has __init/__exit mismatches

this commit:
commit 1be95f401657e75984871c369d774d507e462939
Author: Tejun Heo <tj@...nel.org>
Date:   Thu Aug 28 16:42:51 2008 +0200
sound: make OSS sound core optional

results in this failure:
WARNING: vmlinux.o(.init.text+0xfbf0): Section mismatch in reference
from the function _init_soundcore() to the function
.exit.text:_cleanup_oss_soundcore()
The function __init _init_soundcore() references
a function __exit _cleanup_oss_soundcore().
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
_cleanup_oss_soundcore() so it may be used outside an exit section.

and can easily be seen in sound/sound_core.c:
...
static int __init init_soundcore(void)
{
...
               cleanup_oss_soundcore();
...
}
...
static void __exit cleanup_oss_soundcore(void)
{
...
}
...
-mike
--
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/