linux-kernel - Re: [PATCH] blk-mq: fix blk_mq_start_stopped_hw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20131007193358.GA14511@infradead.org>
Date:	Mon, 7 Oct 2013 12:33:58 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Christoph Hellwig <hch@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] blk-mq: fix blk_mq_start_stopped_hw_queues from irq
 context

On Sun, Oct 06, 2013 at 12:10:13PM -0600, Jens Axboe wrote:
> Thanks, applied. Might not be a bad idea to just mimic the run queue
> API, and provide a blk_mq_start_hw_queue(hctx, is_async) instead.

I have to see I really don't like this is_async, I'd much preper to
untangle those into separate versions further up the stack similar to
how the old blk_run_queue variants work.

But that'll have to wait a bit anyway, at least until you made a
decision on the plugging patch.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/