commit | 8bdd3f8a6993fef2f364aca6e1a59559405773a2 | [log] [tgz] |
---|---|---|
author | Jens Axboe <jens.axboe@oracle.com> | Fri Feb 01 09:44:28 2008 +0100 |
committer | Jens Axboe <jens.axboe@oracle.com> | Fri Feb 01 09:44:28 2008 +0100 |
tree | cbf07985c3396417932002be5cd5e4f2c47433e9 | |
parent | 4f4f6c2502474f51654a699d7127d86c2f87075a [diff] |
as-iosched: fix inconsistent ioc->lock context Since it's acquired from irq context, all locking must be of the irq safe variant. Most are already inside the queue lock (which already disables interrupts), but the io scheduler rmmod path always has irqs enabled and the put_io_context() path may legally be called with irqs enabled (even if it isn't usually). So fixup those two. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>