All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Schumaker <bjschuma@netapp.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: kernel-janitors@vger.kernel.org,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Linux-NFS <linux-nfs@vger.kernel.org>
Subject: Re: [nfs:nfs-for-bryan 86/99] WARNING: fs/built-in.o(.init.text+0x309d): Section mismatch in referen
Date: Tue, 17 Jul 2012 18:40:19 +0000	[thread overview]
Message-ID: <5005B193.5050306@netapp.com> (raw)
In-Reply-To: <20120717183641.GA6987@localhost>

Thanks for catching these!  I was just looking over these patches again, so I'll fix this up while I'm at it.

- Bryan

On 07/17/2012 02:36 PM, Fengguang Wu wrote:
> Hi Bryan,
> 
> There are new compile warnings show up in
> 
> tree:   git://git.linux-nfs.org/projects/trondmy/linux-nfs.git nfs-for-bryan
> head:   98ff07b7c3bb45b3c5f9fde8231277d45500c2ba
> commit: 129d1977ed39cbb4f091a518e4a12498c04f45ba [86/99] NFS: Create an init_nfs_v4() function
> config: x86_64-allyesdebian (attached as .config)
> 
> All warnings:
> 
> 
> WARNING: fs/built-in.o(.init.text+0x309d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> WARNING: fs/nfs/nfs.o(.init.text+0x17d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> WARNING: fs/nfs/built-in.o(.init.text+0x17d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> WARNING: vmlinux.o(.init.text+0x27f81): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> ---
> 0-DAY kernel build testing backend         Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation
> 



WARNING: multiple messages have this Message-ID (diff)
From: Bryan Schumaker <bjschuma@netapp.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: kernel-janitors@vger.kernel.org,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Linux-NFS <linux-nfs@vger.kernel.org>
Subject: Re: [nfs:nfs-for-bryan 86/99] WARNING: fs/built-in.o(.init.text+0x309d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
Date: Tue, 17 Jul 2012 14:40:19 -0400	[thread overview]
Message-ID: <5005B193.5050306@netapp.com> (raw)
In-Reply-To: <20120717183641.GA6987@localhost>

Thanks for catching these!  I was just looking over these patches again, so I'll fix this up while I'm at it.

- Bryan

On 07/17/2012 02:36 PM, Fengguang Wu wrote:
> Hi Bryan,
> 
> There are new compile warnings show up in
> 
> tree:   git://git.linux-nfs.org/projects/trondmy/linux-nfs.git nfs-for-bryan
> head:   98ff07b7c3bb45b3c5f9fde8231277d45500c2ba
> commit: 129d1977ed39cbb4f091a518e4a12498c04f45ba [86/99] NFS: Create an init_nfs_v4() function
> config: x86_64-allyesdebian (attached as .config)
> 
> All warnings:
> 
> 
> WARNING: fs/built-in.o(.init.text+0x309d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> WARNING: fs/nfs/nfs.o(.init.text+0x17d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> WARNING: fs/nfs/built-in.o(.init.text+0x17d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> WARNING: vmlinux.o(.init.text+0x27f81): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4()
> The function __init init_nfs_fs() references
> a function __exit exit_nfs_v4().
> 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
> exit_nfs_v4() so it may be used outside an exit section.
> 
> ---
> 0-DAY kernel build testing backend         Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation
> 



       reply	other threads:[~2012-07-17 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120717183641.GA6987@localhost>
2012-07-17 18:40 ` Bryan Schumaker [this message]
2012-07-17 18:40   ` [nfs:nfs-for-bryan 86/99] WARNING: fs/built-in.o(.init.text+0x309d): Section mismatch in reference from the function init_nfs_fs() to the function .exit.text:exit_nfs_v4() Bryan Schumaker

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=5005B193.5050306@netapp.com \
    --to=bjschuma@netapp.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=fengguang.wu@intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.