summaryrefslogtreecommitdiffstats
path: root/fs/ioprio.c
diff options
context:
space:
mode:
authorOleg Nesterov <oleg@tv-sign.ru>2006-08-29 09:15:14 +0200
committerJens Axboe <axboe@nelson.home.kernel.dk>2006-09-30 20:31:18 +0200
commit25034d7a83cf77667f3d65822484b305d4be6b25 (patch)
tree7e4d432aae0cab93c22e692ceceffe2b5f7500d6 /fs/ioprio.c
parent9bf09c23853bb8009625c2ec60dc6beb9472d3ca (diff)
downloadop-kernel-dev-25034d7a83cf77667f3d65822484b305d4be6b25.zip
op-kernel-dev-25034d7a83cf77667f3d65822484b305d4be6b25.tar.gz
[PATCH] exit_io_context: don't disable irqs
We don't need to disable irqs to clear current->io_context, it is protected by ->alloc_lock. Even IF it was possible to submit I/O from IRQ on behalf of current this irq_disable() can't help: current_io_context() will re-instantiate ->io_context after irq_enable(). We don't need task_lock() or local_irq_disable() to clear ioc->task. This can't prevent other CPUs from playing with our io_context anyway. Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/ioprio.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud