diff options
| author | Oleg Nesterov <oleg@tv-sign.ru> | 2006-08-21 08:34:15 +0200 |
|---|---|---|
| committer | Jens Axboe <axboe@suse.de> | 2006-08-21 08:34:15 +0200 |
| commit | 9f83e45eb54fc7198dc59fc63255341851ba4c48 (patch) | |
| tree | 3874581e08052b7f37f164110b3bd44ae5eff291 /Kbuild | |
| parent | 78bd4d484f81a611ef6ff02f909e576cb9aac7f2 (diff) | |
| download | linux-9f83e45eb54fc7198dc59fc63255341851ba4c48.tar.gz linux-9f83e45eb54fc7198dc59fc63255341851ba4c48.tar.bz2 linux-9f83e45eb54fc7198dc59fc63255341851ba4c48.zip | |
[PATCH] Fix current_io_context() vs set_task_ioprio() race
I know nothing about io scheduler, but I suspect set_task_ioprio() is not safe.
current_io_context() initializes "struct io_context", then sets ->io_context.
set_task_ioprio() running on another cpu may see the changes out of order, so
->set_ioprio(ioc) may use io_context which was not initialized properly.
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Signed-off-by: Jens Axboe <axboe@suse.de>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions