On Fri, Jul 7, 2017 at 9:45 PM, Stefan Haberland
wrote:
> While changing the DASD device driver to use the blk-mq interfaces I found
> the following unexpected behavior:
>
> In case of a timeout our complete callback is never called. Here is the
> sequence of events as I understood:
>
> - timeout
While changing the DASD device driver to use the blk-mq interfaces I
found the following unexpected behavior:
In case of a timeout our complete callback is never called. Here is the
sequence of events as I understood:
- timeout occurs
- blk_mq_check_expired() calls and checks blk_mark_rq_comp
2 matches
Mail list logo
