tree 7e4d432aae0cab93c22e692ceceffe2b5f7500d6
parent 9bf09c23853bb8009625c2ec60dc6beb9472d3ca
author Oleg Nesterov <oleg@tv-sign.ru> 1156835714 +0200
committer Jens Axboe <axboe@nelson.home.kernel.dk> 1159641078 +0200

[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>