From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Trond Myklebust <trond.myklebust@fys•uio.no>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build failure after merge of the final tree (nfs tree related)
Date: Wed, 4 Aug 2010 14:54:06 +1000 [thread overview]
Message-ID: <20100804145406.f0fc5ea4.sfr@canb.auug.org.au> (raw)
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:
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Wed, 4 Aug 2010 14:48:54 +1000
Subject: [PATCH] nfs: remove __exit from rpc_destroy_authunix
since it is referenced from an __init function.
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
include/linux/sunrpc/auth.h | 2 +-
net/sunrpc/auth_unix.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/sunrpc/auth.h b/include/linux/sunrpc/auth.h
index d9d1402..652f2da 100644
--- a/include/linux/sunrpc/auth.h
+++ b/include/linux/sunrpc/auth.h
@@ -124,7 +124,7 @@ int __init rpc_init_generic_auth(void);
int __init rpcauth_init_module(void);
void __exit rpcauth_remove_module(void);
void __exit rpc_destroy_generic_auth(void);
-void __exit rpc_destroy_authunix(void);
+void rpc_destroy_authunix(void);
struct rpc_cred * rpc_lookup_cred(void);
struct rpc_cred * rpc_lookup_machine_cred(void);
diff --git a/net/sunrpc/auth_unix.c b/net/sunrpc/auth_unix.c
index 6385af7..4cb70dc 100644
--- a/net/sunrpc/auth_unix.c
+++ b/net/sunrpc/auth_unix.c
@@ -207,7 +207,7 @@ int __init rpc_init_authunix(void)
return rpcauth_init_credcache(&unix_auth);
}
-void __exit rpc_destroy_authunix(void)
+void rpc_destroy_authunix(void)
{
rpcauth_destroy_credcache(&unix_auth);
}
--
1.7.1
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
next reply other threads:[~2010-08-04 4:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 4:54 Stephen Rothwell [this message]
2010-08-04 12:58 ` linux-next: build failure after merge of the final tree (nfs tree related) Trond Myklebust
-- 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=20100804145406.f0fc5ea4.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=trond.myklebust@fys$(echo .)uio.no \
/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