linux-kernel - Re: [PATCH] bluetooth rfcomm: fix section mismatch warning

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]

Message-ID: <20100802170136.GA19526@vigoh>
Date:	Mon, 2 Aug 2010 14:01:37 -0300
From:	"Gustavo F. Padovan" <padovan@...fusion.mobi>
To:	Axel Lin <axel.lin@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Marcel Holtmann <marcel@...tmann.org>
Subject: Re: [PATCH] bluetooth rfcomm: fix section mismatch warning

Hi Axel,

* Axel Lin <axel.lin@...il.com> [2010-08-02 16:16:16 +0800]:

> Introduced by Commit 2f8362afcd2da8b313ec3cc04a50af19d3592972
> ( Bluetooth: Add __init and __exit marks to RFCOMM )
> 
> WARNING: vmlinux.o(.init.text+0x246d1): Section mismatch in reference from the function rfcomm_init() to the function .exit.text:rfcomm_cleanup_ttys()
> The function __init rfcomm_init() references
> a function __exit rfcomm_cleanup_ttys().
> 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
> rfcomm_cleanup_ttys() so it may be used outside an exit section.
> 
> This patch removes the __exit annotation from rfcomm_cleanup_ttys to eliminate the warning.
> 
> Signed-off-by: Axel Lin <axel.lin@...il.com>
> ---
>  net/bluetooth/rfcomm/tty.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

We have fixed that already. Thanks anyway. ;)

-- 
Gustavo F. Padovan
ProFUSION embedded systems - http://profusion.mobi
--
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/