* [linux-next-20130822] module: broken module versions?
@ 2013-08-26 14:06 Tetsuo Handa
2013-08-27 10:23 ` Tetsuo Handa
[not found] ` <201308270214.r7R2EXES054735@www262.sakura.ne.jp>
0 siblings, 2 replies; 6+ messages in thread
From: Tetsuo Handa @ 2013-08-26 14:06 UTC (permalink / raw)
To: ak, viro, geert, akpm, dhowells, rusty; +Cc: linux-kernel
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 symbol current_fs_time (err -22)
ipv6: disagrees about version of symbol sock_register
ipv6: Unknown symbol sock_register (err -22)
ipv6: disagrees about version of symbol ns_capable
ipv6: Unknown symbol ns_capable (err -22)
next-20130815 worked OK.
I guess that the culprit commit touches something module related code but I'm
unable to run full bisection due to unbootable 3.11-rc5. Any clue?
Config is at http://I-love.SAKURA.ne.jp/tmp/config-3.11-rc6-next-20130822 .
----------
# bad: [66a01bae29d11916c09f9f5a937cafe7d402e4a5] Add linux-next specific files for 20130819
# good: [49dfe76261e427f5521b40321fbc3d947350165d] Documentation: add networking/netdev-FAQ.txt
# good: [cf3c4c03060b688cbc389ebc5065ebcce5653e96] 8139cp: Add dma_mapping_error checking
# good: [093aba10e6a88a28fdc7d6ee8ec69aebd9767a22] Merge branch 'for-3.12/upstream' into for-next
# good: [d010e5769a5ab2ae8d2bcb36e77b98172c24d80c] PCI / ACPI: Use dev_dbg() instead of dev_info() in acpi_pci_set_power_state()
# good: [569935db80fd5338005d977ffc3428d43aad84ba] Merge branches 'cma', 'cxgb3', 'cxgb4', 'ipoib', 'misc', 'mlx4', 'mlx5', 'nes', 'ocrdma' and 'qib' into for-next
# good: [e729eac6f65e11c5f03b09adcc84bd5bcb230467] udf: Refuse RW mount of the filesystem instead of making it RO
# good: [3fef7f795fff7ccc58d55a28315ca73305515884] Merge remote-tracking branch 'asoc/fix/wm0010' into asoc-linus
# good: [11a45820d02ee78ad22bb95d5abb94950a355d8d] Merge tag 'nfc-fixes-3.11-2' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-fixes
# good: [8fe120b5a665fc869c23f86e4964b801f6e53486] ASoC: omap-abe-twl6040: Remove support for pdata (legacy boot)
# good: [66ffd113f5d81e951b0379acfd0a1df0771d8828] cifs: set sb->s_d_op before calling d_make_root()
# good: [6a3fc31f35025a583499c0d3b1c6fc5dcf6e48ec] spi/ep93xx: Fix format specifier warning
# good: [2de024b766bb9e31c357f70c6344d1107f38ce1a] spi/atmel: Fix format specifier warnings
# good: [e56566699ca64ec44dd134ec5310a3585ffacfec] regulator: pfuze100: Simplify pfuze100_set_ramp_delay implementation
# good: [6878ea72a5d1aa6caae86449975a50b7fe9abed5] aio: be defensive to ensure request batching is non-zero instead of BUG_ON()
# good: [70263cb474853c116f80713d468f3c17d805921c] ASoC: rcar: fix return value check in rsnd_gen1_probe()
# good: [3f1a91aa25579ba5e7268a47a73d2a83e4802c62] ASoC: fsl: Fix module build
# good: [db5ff9541b61ef8394bad0fb05508921b8c5b17b] ASoC: spdif: Add S20_3LE and S24_LE support for dummy codec drivers
# good: [01c6a6afd50f07dfd66b2891fd194c4b789fca48] x86 / tboot / ACPI: Fail extended mode reduced hardware sleep
# good: [21aa521727a004ce4a4c46e9a5cb7e34619b4d16] ARM: dts: Add G2D support to exynos5250
# good: [7b4e0c4ac1809eab6fcfe6818ec8b70be79b41bc] ACPI / PM: Remove redundant power manageable check from acpi_bus_set_power()
# good: [d29cae9f8f2a056138d1bfc55de6e5aa9b9c6a93] Merge branch 'for-3.12' into for-next
# good: [b36f4be3de1b123d8601de062e7dbfc904f305fb] Linux 3.11-rc6
# good: [d4e4ab86bcba5a72779c43dc1459f71fea3d89c8] Linux 3.11-rc5
# good: [c095ba7224d8edc71dcef0d655911399a8bd4a3f] Linux 3.11-rc4
# good: [5ae90d8e467e625e447000cb4335c4db973b1095] Linux 3.11-rc3
# good: [3b2f64d00c46e1e4e9bd0bb9bb12619adac27a4b] Linux 3.11-rc2
# good: [ad81f0545ef01ea651886dddac4bef6cec930092] Linux 3.11-rc1
# good: [8bb495e3f02401ee6f76d1b1d77f3ac9f079e376] Linux 3.10
# good: [c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1] Linux 3.9
# good: [19f949f52599ba7c3f67a5897ac6be14bfcb1200] Linux 3.8
# good: [29594404d7fe73cd80eaa4ee8c43dcc53970c60e] Linux 3.7
# good: [a0d271cbfed1dd50278c6b06bead3d00ba0a88f9] Linux 3.6
# good: [28a33cbc24e4256c143dce96c7d93bf423229f92] Linux 3.5
# good: [76e10d158efb6d4516018846f60c2ab5501900bc] Linux 3.4
# good: [c16fa4f2ad19908a47c63d8fa436a1178438c7e7] Linux 3.3
# good: [805a6af8dba5dfdd35ec35dc52ec0122400b2610] Linux 3.2
# good: [c3b92c8787367a8bb53d57d9789b558f1295cc96] Linux 3.1
# good: [02f8c6aee8df3cdc935e9bdd4f2d020306035dbe] Linux 3.0
git bisect start '66a01bae29d11916c09f9f5a937cafe7d402e4a5' '49dfe76261e427f5521b40321fbc3d947350165d' 'cf3c4c03060b688cbc389ebc5065ebcce5653e96' \
'093aba10e6a88a28fdc7d6ee8ec69aebd9767a22' 'd010e5769a5ab2ae8d2bcb36e77b98172c24d80c' '569935db80fd5338005d977ffc3428d43aad84ba' \
'e729eac6f65e11c5f03b09adcc84bd5bcb230467' '3fef7f795fff7ccc58d55a28315ca73305515884' '11a45820d02ee78ad22bb95d5abb94950a355d8d' \
'8fe120b5a665fc869c23f86e4964b801f6e53486' '66ffd113f5d81e951b0379acfd0a1df0771d8828' '6a3fc31f35025a583499c0d3b1c6fc5dcf6e48ec' \
'2de024b766bb9e31c357f70c6344d1107f38ce1a' 'e56566699ca64ec44dd134ec5310a3585ffacfec' '6878ea72a5d1aa6caae86449975a50b7fe9abed5' \
'70263cb474853c116f80713d468f3c17d805921c' '3f1a91aa25579ba5e7268a47a73d2a83e4802c62' 'db5ff9541b61ef8394bad0fb05508921b8c5b17b' \
'01c6a6afd50f07dfd66b2891fd194c4b789fca48' '21aa521727a004ce4a4c46e9a5cb7e34619b4d16' '7b4e0c4ac1809eab6fcfe6818ec8b70be79b41bc' \
'd29cae9f8f2a056138d1bfc55de6e5aa9b9c6a93' 'v3.11-rc6' 'v3.11-rc5' 'v3.11-rc4' 'v3.11-rc3' 'v3.11-rc2' 'v3.11-rc1' 'v3.10' 'v3.9' \
'v3.8' 'v3.7' 'v3.6' 'v3.5' 'v3.4' 'v3.3' 'v3.2' 'v3.1' 'v3.0'
# good: [e5e51a9b0965706638be2168de81bfd710402efa] Merge remote-tracking branch 'spi/for-next'
git bisect good e5e51a9b0965706638be2168de81bfd710402efa
# good: [0dbd9fe04c180edc33dc6bc23d0691f8575e3d60] Merge remote-tracking branch 'staging/staging-next'
git bisect good 0dbd9fe04c180edc33dc6bc23d0691f8575e3d60
# good: [194523e2d5dcb680b56d7817730c7b94155ec49c] Merge remote-tracking branch 'msm/for-next'
git bisect good 194523e2d5dcb680b56d7817730c7b94155ec49c
# good: [75c1f84c2dd22e58ecbfcfd7789bbd2b8ab90192] Merge remote-tracking branch 'aio/master'
git bisect good 75c1f84c2dd22e58ecbfcfd7789bbd2b8ab90192
# skip: [a1f8eee9bd6041e05003d86598aef6878f6135a8] MAINTAINERS: SI4713: fix file pattern
git bisect skip a1f8eee9bd6041e05003d86598aef6878f6135a8
# skip: [92a8363db29864b9766d3c0ad0b551d55e640acc] mm/hotplug: remove stop_machine() from try_offline_node()
git bisect skip 92a8363db29864b9766d3c0ad0b551d55e640acc
# bad: [cd857ff4dd4c7cba3849ababe179b0a828167617] xfs: fix dquot isolation hang
git bisect bad cd857ff4dd4c7cba3849ababe179b0a828167617
# skip: [df708487cbd4a49b7fb1a21cfa5578aaef113be4] efs: iget_locked() doesn't return an ERR_PTR()
git bisect skip df708487cbd4a49b7fb1a21cfa5578aaef113be4
# skip: [d112c138b32f46699b594e009e588f0829a94478] mm/zswap: use postorder iteration when destroying rbtree
git bisect skip d112c138b32f46699b594e009e588f0829a94478
# skip: [d7355ae0bce3c19ff5c44af5c5cf6e37c3a42b54] scripts/mod/modpost.c: handle non ABS crc symbols
git bisect skip d7355ae0bce3c19ff5c44af5c5cf6e37c3a42b54
# skip: [fc9d0bf4433ca996825815b8052530abdeaaac23] s390/vmcore: use vmcore for zfcpdump
git bisect skip fc9d0bf4433ca996825815b8052530abdeaaac23
----------
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-next-20130822] module: broken module versions?
2013-08-26 14:06 [linux-next-20130822] module: broken module versions? Tetsuo Handa
@ 2013-08-27 10:23 ` Tetsuo Handa
2013-09-03 11:31 ` [linux-next-20130903] " Tetsuo Handa
[not found] ` <201308270214.r7R2EXES054735@www262.sakura.ne.jp>
1 sibling, 1 reply; 6+ messages in thread
From: Tetsuo Handa @ 2013-08-27 10:23 UTC (permalink / raw)
To: ak, viro, geert, akpm; +Cc: dhowells, rusty, linux-kernel
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
symbol __crc_task_nice has crc=0 sym->st_shndx=0
symbol __crc_vfs_fsync_range has crc=0 sym->st_shndx=0
symbol __crc___symbol_put has crc=0 sym->st_shndx=0
symbol __crc_iov_shorten has crc=0 sym->st_shndx=0
symbol __crc_inode_add_bytes has crc=0 sym->st_shndx=0
symbol __crc_sock_register has crc=0 sym->st_shndx=0
symbol __crc_vm_brk has crc=0 sym->st_shndx=0
symbol __crc_kern_mount_data has crc=0 sym->st_shndx=0
symbol __crc_schedule_timeout has crc=0 sym->st_shndx=0
symbol __crc_generic_getxattr has crc=0 sym->st_shndx=0
symbol __crc_in_group_p has crc=0 sym->st_shndx=0
symbol __crc_finish_open has crc=0 sym->st_shndx=0
symbol __crc_get_unmapped_area has crc=0 sym->st_shndx=0
symbol __crc_generic_write_sync has crc=0 sym->st_shndx=0
symbol __crc_filp_close has crc=0 sym->st_shndx=0
symbol __crc_d_tmpfile has crc=0 sym->st_shndx=0
symbol __crc_iterate_fd has crc=0 sym->st_shndx=0
symbol __crc_register_exec_domain has crc=0 sym->st_shndx=0
symbol __crc_ns_capable has crc=0 sym->st_shndx=0
symbol __crc___page_file_mapping has crc=0 sym->st_shndx=0
symbol __crc_mnt_set_expiry has crc=0 sym->st_shndx=0
symbol __crc_do_sync_read has crc=0 sym->st_shndx=0
symbol __crc_vfs_test_lock has crc=0 sym->st_shndx=0
symbol __crc_perf_event_create_kernel_counter has crc=0 sym->st_shndx=0
symbol __crc_current_fs_time has crc=0 sym->st_shndx=0
symbol __crc_softirq_work_list has crc=0 sym->st_shndx=0
symbol __crc_sys_close has crc=0 sym->st_shndx=0
symbol __crc_path_is_under has crc=0 sym->st_shndx=0
symbol __crc_task_nice has crc=0 sym->st_shndx=0
symbol __crc_vfs_fsync_range has crc=0 sym->st_shndx=0
symbol __crc___symbol_put has crc=0 sym->st_shndx=0
symbol __crc_iov_shorten has crc=0 sym->st_shndx=0
symbol __crc_inode_add_bytes has crc=0 sym->st_shndx=0
symbol __crc_sock_register has crc=0 sym->st_shndx=0
symbol __crc_vm_brk has crc=0 sym->st_shndx=0
symbol __crc_kern_mount_data has crc=0 sym->st_shndx=0
symbol __crc_schedule_timeout has crc=0 sym->st_shndx=0
symbol __crc_generic_getxattr has crc=0 sym->st_shndx=0
symbol __crc_in_group_p has crc=0 sym->st_shndx=0
symbol __crc_finish_open has crc=0 sym->st_shndx=0
symbol __crc_get_unmapped_area has crc=0 sym->st_shndx=0
symbol __crc_generic_write_sync has crc=0 sym->st_shndx=0
symbol __crc_filp_close has crc=0 sym->st_shndx=0
symbol __crc_d_tmpfile has crc=0 sym->st_shndx=0
symbol __crc_iterate_fd has crc=0 sym->st_shndx=0
symbol __crc_register_exec_domain has crc=0 sym->st_shndx=0
symbol __crc_ns_capable has crc=0 sym->st_shndx=0
symbol __crc___page_file_mapping has crc=0 sym->st_shndx=0
symbol __crc_mnt_set_expiry has crc=0 sym->st_shndx=0
symbol __crc_do_sync_read has crc=0 sym->st_shndx=0
symbol __crc_vfs_test_lock has crc=0 sym->st_shndx=0
symbol __crc_perf_event_create_kernel_counter has crc=0 sym->st_shndx=0
symbol __crc_current_fs_time has crc=0 sym->st_shndx=0
symbol __crc_softirq_work_list 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.
Andi, would you check?
Regards.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-next-20130903] module: broken module versions?
2013-08-27 10:23 ` Tetsuo Handa
@ 2013-09-03 11:31 ` Tetsuo Handa
2013-09-04 11:04 ` Tetsuo Handa
0 siblings, 1 reply; 6+ messages in thread
From: Tetsuo Handa @ 2013-09-03 11:31 UTC (permalink / raw)
To: ak, viro, geert, akpm; +Cc: dhowells, rusty, linux-kernel, penguin-kernel
Hello.
This issue is not yet fixed as of linux-next-20130903. Without fixing this
issue, we would get 3.12-rc1 which cannot load several modules.
> I noticed that symbols which cause "disagrees about version of symbol" messages
> have crc == 0.
I tried further debugging but not yet successful.
---------- debug patch start ----------
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -1192,6 +1192,9 @@ static int check_version(Elf_Shdr *sechdrs,
if (strcmp(versions[i].name, symname) != 0)
continue;
+ printk("Found %s checksum %lX vs module %lX\n",
+ versions[i].name, maybe_relocated(*crc, crc_owner),
+ versions[i].crc);
if (versions[i].crc == maybe_relocated(*crc, crc_owner))
return 1;
pr_debug("Found checksum %lX vs module %lX\n",
---------- debug patch end ----------
On x86_64, it shows
Found sock_register checksum 0 vs module 0
Found ns_capable checksum 0 vs module 0
and loading of ipv6.ko succeeds.
On x86_32, it shows
Found sock_register checksum FF100000 vs module 0
Found ns_capable checksum FF100000 vs module 0
and loading of ipv6.ko fails.
Thus, I came to assume that crc == 0 is the expected value but for some reason
crc == 0xFF100000 is recorded into kcrctab tables.
---------- debug patch start ----------
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -320,6 +320,11 @@ bool each_symbol_section(bool (*fn)(const struct symsearch *arr,
#endif
};
+ static unsigned int i;
+ for (; i < __stop___ksymtab - __start___ksymtab; i++)
+ printk("%d crc(%s)=%lx\n", i, __start___ksymtab[i].name,
+ __start___kcrctab[i]);
+
if (each_symbol_in_section(arr, ARRAY_SIZE(arr), NULL, fn, data))
return true;
---------- debug patch end ----------
On x86_64, "grep =0" shows
236 crc(__symbol_put)=0
784 crc(current_fs_time)=0
810 crc(d_tmpfile)=0
955 crc(do_sync_read)=0
1093 crc(filp_close)=0
1107 crc(finish_open)=0
1183 crc(generic_getxattr)=0
1207 crc(generic_write_sync)=0
1237 crc(get_unmapped_area)=0
1335 crc(in_group_p)=0
1407 crc(inode_add_bytes)=0
1495 crc(iov_shorten)=0
1548 crc(iterate_fd)=0
1815 crc(mnt_set_expiry)=0
2038 crc(ns_capable)=0
2102 crc(path_is_under)=0
2405 crc(register_exec_domain)=0
2506 crc(schedule_timeout)=0
2911 crc(sock_register)=0
2922 crc(softirq_work_list)=0
2996 crc(sys_close)=0
3022 crc(task_nice)=0
3243 crc(vfs_fsync_range)=0
3270 crc(vm_brk)=0
On x86_32, "grep =ff100000" shows
244 crc(__symbol_put)=ff100000
784 crc(current_fs_time)=ff100000
810 crc(d_tmpfile)=ff100000
967 crc(do_sync_read)=ff100000
1108 crc(filp_close)=ff100000
1122 crc(finish_open)=ff100000
1198 crc(generic_getxattr)=ff100000
1222 crc(generic_write_sync)=ff100000
1253 crc(get_unmapped_area)=ff100000
1351 crc(in_group_p)=ff100000
1423 crc(inode_add_bytes)=ff100000
1510 crc(iov_shorten)=ff100000
1567 crc(iterate_fd)=ff100000
1840 crc(mnt_set_expiry)=ff100000
2061 crc(ns_capable)=ff100000
2126 crc(path_is_under)=ff100000
2432 crc(register_exec_domain)=ff100000
2535 crc(schedule_timeout)=ff100000
2940 crc(sock_register)=ff100000
2951 crc(softirq_work_list)=ff100000
3013 crc(sys_close)=ff100000
3039 crc(task_nice)=ff100000
3261 crc(vfs_fsync_range)=ff100000
3288 crc(vm_brk)=ff100000
Module.symvers says that these symbols have crc == 0x00000000 and
kcrctab on x86_64 says that these symbols have crc == 0x00000000 but
kcrctab on x86_32 says that these symbols have crc == 0xff100000.
Prior to commit 5c019369 "syscalls.h: use gcc alias instead of assembler
aliases for syscalls", only crc(softirq_work_list)=ff100000 line was shown.
I don't know where 0xff100000 comes from, but this value is kconfig dependent
and this value might be by error introduced.
I also tried older kernels. As far as I tested (I might be wrong as this value
is kconfig dependent), it seems that 3.9 and later kernels show
crc(softirq_work_list)=ff100000 line while 3.8 and earlier kernels show
crc(softirq_work_list)=0 line. I'll try to bisect between 3.8 and 3.9 if this
change is by error introduced.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-next-20130903] module: broken module versions?
2013-09-03 11:31 ` [linux-next-20130903] " Tetsuo Handa
@ 2013-09-04 11:04 ` Tetsuo Handa
0 siblings, 0 replies; 6+ messages in thread
From: Tetsuo Handa @ 2013-09-04 11:04 UTC (permalink / raw)
To: ak, viro, geert, akpm; +Cc: dhowells, rusty, linux-kernel
Hello.
Tetsuo Handa wrote:
> I tried further debugging but not yet successful.
I found what was wrong.
Bad kernel config contained
CONFIG_PHYSICAL_START=0x1000000
CONFIG_PHYSICAL_ALIGN=0x100000
whereas good kernel config contained
CONFIG_PHYSICAL_START=0x1000000
CONFIG_PHYSICAL_ALIGN=0x1000000
. I think that there is no constraint checking for these values and resulted in
overlaying something on the kcrctab table.
Now linux-next-20130903 works fine. Thank you.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-next-20130822] module: broken module versions?
[not found] ` <201308270214.r7R2EXES054735@www262.sakura.ne.jp>
@ 2013-09-11 0:23 ` Andrew Morton
2013-09-11 3:44 ` Tetsuo Handa
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2013-09-11 0:23 UTC (permalink / raw)
To: penguin-kernel; +Cc: ak, viro, geert, dhowells, rusty, linux-kernel
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [linux-next-20130822] module: broken module versions?
2013-09-11 0:23 ` [linux-next-20130822] " Andrew Morton
@ 2013-09-11 3:44 ` Tetsuo Handa
0 siblings, 0 replies; 6+ messages in thread
From: Tetsuo Handa @ 2013-09-11 3:44 UTC (permalink / raw)
To: Andrew Morton; +Cc: ak, viro, geert, dhowells, rusty, linux-kernel
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 patches.
Regards.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-09-11 3:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-26 14:06 [linux-next-20130822] module: broken module versions? 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 ` [linux-next-20130822] " Andrew Morton
2013-09-11 3:44 ` Tetsuo Handa
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®