From: Andrew Morton <akpm@linux-foundation.org>
To: penguin-kernel@i-love.sakura.ne.jp
Cc: ak@linux.intel.com, viro@ZenIV.linux.org.uk,
geert@linux-m68k.org, dhowells@redhat.com, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: [linux-next-20130822] module: broken module versions?
Date: Tue, 10 Sep 2013 17:23:21 -0700 [thread overview]
Message-ID: <20130910172321.0392fea32f2a33e629a8204c@linux-foundation.org> (raw)
In-Reply-To: <201308270214.r7R2EXES054735@www262.sakura.ne.jp>
On Tue, 27 Aug 2013 11:14:33 +0900 penguin-kernel@i-love.sakura.ne.jp wrote:
> I noticed that symbols which cause "disagrees about version of symbol" messages
> have crc == 0.
>
> ---------- scripts/mod/modpost.c ----------
> /* CRC'd symbol */
> if (strncmp(symname, CRC_PFX, strlen(CRC_PFX)) == 0) {
> crc = (unsigned int) sym->st_value;
> + if (!crc)
> + fprintf(stderr, "symbol %s has crc=0 sym->st_shndx=%d\n",
> + symname, sym->st_shndx);
> sym_update_crc(symname + strlen(CRC_PFX), mod, crc,
> export);
> }
> ---------- scripts/mod/modpost.c ----------
>
> I got below messages upon build.
>
> symbol __crc_sys_close has crc=0 sym->st_shndx=0
> symbol __crc_path_is_under has crc=0 sym->st_shndx=0
>
> ...
>
> I continued bisection in this way and found that commit 5c019369 "syscalls.h:
> use gcc alias instead of assembler aliases for syscalls" started showing
> below messages upon build.
>
> WARNING: "ns_capable" [net/ipv6/sit.ko] has no CRC!
> WARNING: "ns_capable" [net/ipv6/ipv6.ko] has no CRC!
> WARNING: "sock_register" [net/ipv6/ipv6.ko] has no CRC!
> WARNING: "ns_capable" [net/ipv4/ip_tunnel.ko] has no CRC!
> WARNING: "inode_add_bytes" [fs/udf/udf.ko] has no CRC!
> WARNING: "current_fs_time" [fs/udf/udf.ko] has no CRC!
> WARNING: "do_sync_read" [fs/udf/udf.ko] has no CRC!
> WARNING: "d_tmpfile" [fs/udf/udf.ko] has no CRC!
> WARNING: "sys_close" [fs/binfmt_misc.ko] has no CRC!
> WARNING: "current_fs_time" [fs/binfmt_misc.ko] has no CRC!
> WARNING: "vm_brk" [fs/binfmt_aout.ko] has no CRC!
> WARNING: "sys_close" [fs/autofs4/autofs4.ko] has no CRC!
> WARNING: "schedule_timeout" [drivers/hid/usbhid/usbhid.ko] has no CRC!
>
> Reverting commit 5c019369 from linux-next-20130822 solved this problem.
OK, thanks, I've dropped
syscallsh-use-gcc-alias-instead-of-assembler-aliases-for-syscalls.patch
and scripts-mod-modpostc-handle-non-abs-crc-symbols.patch.
next prev parent reply other threads:[~2013-09-11 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 14:06 Tetsuo Handa
2013-08-27 10:23 ` Tetsuo Handa
2013-09-03 11:31 ` [linux-next-20130903] " Tetsuo Handa
2013-09-04 11:04 ` Tetsuo Handa
[not found] ` <201308270214.r7R2EXES054735@www262.sakura.ne.jp>
2013-09-11 0:23 ` Andrew Morton [this message]
2013-09-11 3:44 ` [linux-next-20130822] " Tetsuo Handa
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=20130910172321.0392fea32f2a33e629a8204c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rusty@rustcorp.com.au \
--cc=viro@ZenIV.linux.org.uk \
/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®