From: Randy Dunlap <randy.dunlap@oracle.com>
To: Fred Isaman <iisaman@citi.umich.edu>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: potential linking bug in recursive directory descent
Date: Tue, 24 Feb 2009 11:19:44 -0800 [thread overview]
Message-ID: <49A44850.5010905@oracle.com> (raw)
In-Reply-To: <b493f8670902241105l48bd7cdbmb99608e802d2454a@mail.gmail.com>
Fred Isaman wrote:
> The pnfs tree base of of 2.6.29-rc5 uses the new find_last_bit
Where is the pnfs tree?
> function (defined in
> lib/find_last_bit.c) in a file in the fs/nfs directory. Myself and
> another developer (though no one else so far) get the following error
> during compile:
>
> Kernel: arch/x86/boot/bzImage is ready (#5)
> Building modules, stage 2.
> MODPOST 515 modules
> ERROR: "find_last_bit" [fs/nfs/nfs.ko] undefined!
> make[2]: *** [__modpost] Error 1
> make[1]: *** [modules] Error 2
> make: *** [sub-make] Error 2
>
>
> Note that find_last_bit() is not used in any file in the fs directory.
> If I add it to any function that is EXPORT_SYMBOL'ed
> from the fs directory, suddenly the compile errors go away. (See the
> below patch for a more concrete example.)
>
> I am not sure what is going on, and why it only affects some
> developers, but it looks a lot like the kbuild system
> is deciding that the library does not need to be included at the fs
> directory level, so isn't including it in fs/nfs where
> it is needed.
>
> Thanks for any help.
> Fred
A failing .config file would be helpful.
Is CONFIG_GENERIC_FIND_LAST_BIT set in your .config file?
If you change lib/Makefile like this:
-lib-$(CONFIG_GENERIC_FIND_LAST_BIT) += find_last_bit.o
+obj-$(CONFIG_GENERIC_FIND_LAST_BIT) += find_last_bit.o
i.e., s/lib/obj/, does your build succeed?
> From 4bd89543983640ab01c9b704d427f83dad3aa455 Mon Sep 17 00:00:00 2001
> From: Fred Isaman <iisaman@citi.umich.edu>
> Date: Fri, 20 Feb 2009 11:58:52 -0500
> Subject: [PATCH 1/1] DEBUG: Need this to compile - what the heck?
>
> This looks suspiciously like a bug in the kbuild system, where
> the library include is not passed down to fs/nfs unless it is
> used by fs. Without this, I get the following error during linking:
>
> Kernel: arch/x86/boot/bzImage is ready (#5)
> Building modules, stage 2.
> MODPOST 515 modules
> ERROR: "find_last_bit" [fs/nfs/nfs.ko] undefined!
> make[2]: *** [__modpost] Error 1
> make[1]: *** [modules] Error 2
> make: *** [sub-make] Error 2
>
> Signed-off-by: Fred Isaman <iisaman@citi.umich.edu>
> ---
> fs/inode.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/fs/inode.c b/fs/inode.c
> index 306faef..a4e29b3 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -226,6 +226,7 @@ EXPORT_SYMBOL(destroy_inode);
> */
> void inode_init_once(struct inode *inode)
> {
> + find_last_bit((unsigned long *) inode, 5);
> memset(inode, 0, sizeof(*inode));
> INIT_HLIST_NODE(&inode->i_hash);
> INIT_LIST_HEAD(&inode->i_dentry);
> --
--
~Randy
next prev parent reply other threads:[~2009-02-24 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 19:05 potential linking bug in recursive directory descent Fred Isaman
2009-02-24 19:19 ` Randy Dunlap [this message]
2009-02-24 20:19 ` Fred Isaman
2009-02-24 21:03 ` Sam Ravnborg
2009-02-24 21:20 ` Fred Isaman
2009-02-24 21:28 ` Randy Dunlap
2009-02-25 1:04 ` Fred Isaman
2009-02-24 21:46 ` 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=49A44850.5010905@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=iisaman@citi.umich.edu \
--cc=linux-kbuild@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox