Hi,
Please apply [1] to stable 5.8.9+, as it fixed nvme-loop connecting failure issue[2].
[1] 64d452b3560b nvme-loop: set ctrl state connecting after init
[2] https://lists.linaro.org/pipermail/linux-stable-mirror/2020-September/216482...
Best Regards, Yi Zhang
On Wed, Sep 16, 2020 at 11:37:57AM -0400, Yi Zhang wrote:
Hi,
Please apply [1] to stable 5.8.9+, as it fixed nvme-loop connecting failure issue[2].
[1] 64d452b3560b nvme-loop: set ctrl state connecting after init
[2] https://lists.linaro.org/pipermail/linux-stable-mirror/2020-September/216482...
So the "Fixes:" tag in the commit lies?
I would like to get an ack from the maintainers/developers on that patch before I queue it up.
thanks,
greg k-h
Hi,
Please apply [1] to stable 5.8.9+, as it fixed nvme-loop connecting failure issue[2].
[1] 64d452b3560b nvme-loop: set ctrl state connecting after init
[2] https://lists.linaro.org/pipermail/linux-stable-mirror/2020-September/216482...
So the "Fixes:" tag in the commit lies?
I would like to get an ack from the maintainers/developers on that patch before I queue it up.
Acked-by: Sagi Grimberg sagi@grimberg.me
This went in citing the wrong git hash, our mistake.
Actually, the cited offending commit had a fixes tag itself that goes back further[1]... Which means that this needs to go with that, what's the procedure to take this along with that one?
[1]: 73a5379937ec ("nvme-fabrics: allow to queue requests for live queues") has: Fixes: 35897b920c8a ("nvme-fabrics: fix and refine state checks in __nvmf_check_ready")
On Thu, Sep 17, 2020 at 11:50:27AM -0700, Sagi Grimberg wrote:
Hi,
Please apply [1] to stable 5.8.9+, as it fixed nvme-loop connecting failure issue[2].
[1] 64d452b3560b nvme-loop: set ctrl state connecting after init
[2] https://lists.linaro.org/pipermail/linux-stable-mirror/2020-September/216482...
So the "Fixes:" tag in the commit lies?
I would like to get an ack from the maintainers/developers on that patch before I queue it up.
Acked-by: Sagi Grimberg sagi@grimberg.me
This went in citing the wrong git hash, our mistake.
Actually, the cited offending commit had a fixes tag itself that goes back further[1]... Which means that this needs to go with that, what's the procedure to take this along with that one?
has: Fixes: 35897b920c8a ("nvme-fabrics: fix and refine state checks in __nvmf_check_ready")
I don't understand, is there some other commit you also want backported? If so, just let us know what it is, and how far back to take it.
thanks,
greg k-h
linux-stable-mirror@lists.linaro.org