Revision be14eb619108fa8b7120eb2c42d66d5f623ae10e authored by Brian King on 10 September 2010, 07:03:21 UTC, committed by Jens Axboe on 10 September 2010, 07:03:21 UTC
While testing CPU DLPAR, the following problem was discovered.
We were DLPAR removing the first CPU, which in this case was
logical CPUs 0-3. CPUs 0-2 were already marked offline and
we were in the process of offlining CPU 3. After marking
the CPU inactive and offline in cpu_disable, but before the
cpu was completely idle (cpu_die), we ended up in __make_request
on CPU 3. There we looked at the topology map to see which CPU
to complete the I/O on and found no CPUs in the cpu_sibling_map.
This resulted in the block layer setting the completion cpu
to be NR_CPUS, which then caused an oops when we tried to
complete the I/O.

Fix this by sanity checking the value we return from blk_cpu_to_group
to be a valid cpu value.

Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
1 parent edce682
History
File Mode Size
dnotify
fanotify
inotify
Kconfig -rw-r--r-- 135 bytes
Makefile -rw-r--r-- 168 bytes
fsnotify.c -rw-r--r-- 9.3 KB
fsnotify.h -rw-r--r-- 1.9 KB
group.c -rw-r--r-- 3.0 KB
inode_mark.c -rw-r--r-- 8.0 KB
mark.c -rw-r--r-- 10.8 KB
notification.c -rw-r--r-- 13.3 KB
vfsmount_mark.c -rw-r--r-- 5.0 KB

back to top