From: Trond Myklebust <trond.myklebust@fys•uio.no>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (nfs tree related)
Date: Wed, 04 Aug 2010 08:58:56 -0400 [thread overview]
Message-ID: <1280926736.3011.24.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20100804145406.f0fc5ea4.sfr@canb.auug.org.au>
On Wed, 2010-08-04 at 14:54 +1000, Stephen Rothwell wrote:
> Hi Trond,
>
> After merging the final tree, today's linux-next build (sparc
> defconfig) failed like this:
>
> `rpc_destroy_authunix' referenced in section `.init.text' of net/built-in.o: defined in discarded section `.exit.text' of net/built-in.o
>
> Caused by commit 4c09a3aef02ef9bfab8322fadde269290563ede2 ("NFS: Ensure
> the AUTH_UNIX credcache is allocated dynamically").
>
> It also caused these warnings:
>
> WARNING: vmlinux.o(.init.text+0x1e3b4): Section mismatch in reference from the f
> unction rpcauth_init_module() to the function .exit.text:rpc_destroy_authunix()
> The function __init rpcauth_init_module() references
> a function __exit rpc_destroy_authunix().
> 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
> rpc_destroy_authunix() so it may be used outside an exit section.
>
> I applied the following patch for today:
Hi Stephen,
Thanks! I've fixed this up in the NFS linux-next tree.
Cheers
Trond
next prev parent reply other threads:[~2010-08-04 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 4:54 linux-next: build failure after merge of the final tree (nfs tree related) Stephen Rothwell
2010-08-04 12:58 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-30 3:58 Stephen Rothwell
2010-09-30 13:08 ` Bryan Schumaker
2012-01-23 2:59 Stephen Rothwell
2012-01-23 18:10 ` Trond Myklebust
2012-01-24 8:38 ` Stanislav Kinsbursky
2012-03-20 8:29 Stephen Rothwell
2012-03-20 13:25 ` Myklebust, Trond
2013-11-18 2:20 Stephen Rothwell
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=1280926736.3011.24.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys$(echo .)uio.no \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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