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: <20120604223341.GA28585@merkur.ravnborg.org>
Date:	Tue, 5 Jun 2012 00:33:41 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	"Zou, Yi" <yi.zou@...el.com>
Cc:	Witold Baryluk <baryluk@....if.uj.edu.pl>,
	"Love, Robert W" <robert.w.love@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"James E.J. Bottomley" <JBottomley@...allels.com>,
	"devel@...n-fcoe.org" <devel@...n-fcoe.org>,
	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>
Subject: Re: Different WARNING:
	drivers/scsi/fcoe/libfcoe.o(.init.text+0x1a): Section mismatch in
	reference from the function init_module() to the function
	.exit.text:fcoe_transport_exit()

> However, fcoe_transport_exit() is called only in module *exit* path by the
> module exit func libfcoe_exit(), not in the init_module error path. Let me 
> take a objdump of the libfcoe.o to see where your above section mismatch warning
> is from. Is this on 32bit only?

static int __init libfcoe_init(void)
{
        int rc = 0;

        rc = fcoe_transport_init();
        if (rc)
                return rc;

        rc = fcoe_sysfs_setup();
        if (rc)
                fcoe_transport_exit();    <=============

        return rc;
}

It is called from __init context here.




static void __exit libfcoe_exit(void)
{
        fcoe_sysfs_teardown();
        fcoe_transport_exit();     <==============
}

And from __exit context here.
This is -rc1.

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