[PATCH 0/5] workqueue: fix bug when numa mapping is changed

2014-12-12 Thread Lai Jiangshan
Workqueue code has an assumption that the numa mapping is stable after system booted. It is incorrectly currently. Yasuaki Ishimatsu hit a allocation failure bug when the numa mapping between CPU and node is changed. This was the last scene: SLUB: Unable to allocate memory on node 2 (gfp=0x80d0)

Re: [PATCH 0/5] workqueue: fix bug when numa mapping is changed

2014-12-17 Thread Yasuaki Ishimatsu
Hi Lai, Sorry for the delay in replying. > Thanks for testing. Would you like to use GDB to print the code of > "workqueue_cpu_up_callback+0x510" ? (gdb) l *workqueue_cpu_up_callback+0x510 0x8108fc30 is in workqueue_cpu_up_callback (include/linux/topology.h:84). 79 #endif 80 81

Re: [PATCH 0/5] workqueue: fix bug when numa mapping is changed

2014-12-12 Thread Yasuaki Ishimatsu
Hi Lai, Thank you for posting the patches. I tried your patches. But the following kernel panic occurred. [ 889.394087] BUG: unable to handle kernel paging request at 0002f3f1 [ 889.395005] IP: [] workqueue_cpu_up_callback+0x510/0x740 [ 889.395005] PGD 17a83067 PUD 0 [ 889.395005] Oop

Re: [PATCH 0/5] workqueue: fix bug when numa mapping is changed

2014-12-14 Thread Lai Jiangshan
On 12/13/2014 01:13 AM, Yasuaki Ishimatsu wrote: > Hi Lai, > > Thank you for posting the patches. I tried your patches. > But the following kernel panic occurred. Hi, Yasuaki, Thanks for testing. Would you like to use GDB to print the code of "workqueue_cpu_up_callback+0x510" ? Thanks, Lai >