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

[Andrew Morton]

On Tue, 27 Aug 2013 11:14:33 +0900 penguin-kernel@xxxxxxxxxxxxxxxxxxx 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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/