> DEFINE_PER_CPU(struct list_head [NR_SOFTIRQS], softirq_work_list); > EXPORT_PER_CPU_SYMBOL(softirq_work_list); > > and it doesn't cause any warning on x86 neither does it on ia64 with > defconfig. softirq_work_list doesn't trigger any warning there, > right? Of the 10 EXPORT_PER_CPU_SYMBOL and 4 EXPORT_PER_CPU_SYMBOL_GPL items on ia64, only __sn_cnodeid_to_nasid and softirq_work_list are arrays. The latter appears not to be actually used by any in-tree modules (janitors: does it need to be exported?). The CRC warning only shows up on a module that uses an exported per-cpu array. There seems to be nothing special about the __sn_cnodeid_to_nasid. When I hacked a module to make a random use of softirq_work_list, it too gave a CRC error. I just tried an x86_64 build with a module also modified to access softirq_work_list. It did NOT get a CRC error. So the x86_64 toolchain doesn't seem to have the same issue as ia64. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
