Re: [linux-next-20130822] module: broken module versions?

2013-09-10 Thread Tetsuo Handa
Hello. Andrew Morton wrote: > 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. The problem was solved ( https://lkml.org/lkml/2013/9/4/188 ) and therefore there is no need to drop these

Re: [linux-next-20130822] module: broken module versions?

2013-09-10 Thread Andrew Morton
On Tue, 27 Aug 2013 11:14:33 +0900 penguin-ker...@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, strle

Re: [linux-next-20130822] module: broken module versions?

2013-08-27 Thread Tetsuo Handa
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; + i

[linux-next-20130822] module: broken module versions?

2013-08-26 Thread Tetsuo Handa
Hello. I'm seeing errors that several symbols have bad header (bad CRC ?) as of linux-next-20130822. binfmt_misc: disagrees about version of symbol sys_close binfmt_misc: Unknown symbol sys_close (err -22) binfmt_misc: disagrees about version of symbol current_fs_time binfmt_misc: Unknown