[PATCH 0/5] NVMe pci fixes, for-4.11

[sagi@grimberg.me (Sagi Grimberg)]

Hi Keith,

> These are some fixes for some more device and CPU hot plug scenarios. The
> end result should fix up a long-standing deadlock caused by requests
> entering a quiesced queue that block blk_mq_freeze_queue_wait forever. I'd
> previously tried to fix that here:
>
>   http://lists.infradead.org/pipermail/linux-nvme/2017-January/007620.html
>
> But that was overly complex and overkill anyway on ending requests that
> could have been successful. This time is much simpler, isolated to the
> nvme driver, and more likely to not fail good IO.

Umm, I have some questions on 5/5, I think we can go ahead and queue
1-4 though.

> This is based off linux-block/for-next because I needed to make use
> of the "was_suspend" bool that was recently added with the Opal patch
> set. I also merged in the nvme git tree for final testing, and noticed
> there is a conflict between the following to commits:
>
>   https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git/commit/?h=for-next&id=06406d81a2d7cfb8abcc4fa6cdfeb8e5897007c5
>   http://git.infradead.org/nvme.git/commitdiff/73494e87734f2c2cd4f9e91e98700cd4fd5f3e05
>
> It's a trivial fix, but I think we gotta sort out our merging flow among
> these trees.

Where is this? I didn't see this set on nvme-4.11?