From: Sam Ravnborg <sam@ravnborg.org>
To: "Zou, Yi" <yi.zou@intel.com>
Cc: Witold Baryluk <baryluk@smp.if.uj.edu.pl>,
"Love, Robert W" <robert.w.love@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
"devel@open-fcoe.org" <devel@open-fcoe.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.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()
Date: Tue, 5 Jun 2012 00:33:41 +0200 [thread overview]
Message-ID: <20120604223341.GA28585@merkur.ravnborg.org> (raw)
In-Reply-To: <138EA028228D124A900F5E6746F3C216286EA866@ORSMSX102.amr.corp.intel.com>
> 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
next prev parent reply other threads:[~2012-06-04 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 16:15 WARNING: arch/x86/built-in.o: Section mismatch in reference from the variable test_nmi_ipi_callback_na to function .ini.text:test_nmi_ipi_callback Witold Baryluk
2012-06-04 14:36 ` Don Zickus
2012-06-04 14:59 ` H. Peter Anvin
2012-06-04 15:08 ` Don Zickus
2012-06-04 16:35 ` Sam Ravnborg
2012-06-04 19:08 ` 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() Witold Baryluk
2012-06-04 19:17 ` Sam Ravnborg
2012-06-04 20:52 ` Zou, Yi
2012-06-04 22:33 ` Sam Ravnborg [this message]
2012-06-04 23:11 ` Zou, Yi
2012-06-06 18:59 ` [PATCH] libfcoe: Fix section mismatch Robert Love
2012-06-06 19:58 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120604223341.GA28585@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=JBottomley@parallels.com \
--cc=baryluk@smp.if.uj.edu.pl \
--cc=devel@open-fcoe.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=robert.w.love@intel.com \
--cc=yi.zou@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®