• J
    as-iosched: fix inconsistent ioc->lock context · 8bdd3f8a
    Jens Axboe 提交于
    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: NJens Axboe <jens.axboe@oracle.com>
    8bdd3f8a
as-iosched.c 38.5 KB