kmemleak complaints in nvme PM

[Christoph Hellwig]

On Sun, Apr 09, 2017 at 03:47:35PM +0300, Sagi Grimberg wrote:
> Hi folks,
>
> I got this kmemleak complaint [1] on nvme-loop (but I'm pretty
> confident it should happen with any nvme transport).
>
> Initial code stare tells me that
> dev_pm_qos_update_user_latency_tolerance() can (and usually will
> in controller initializaion) allocate a dev_pm_qos_request, but I
> didn't see a pairing free of that request.
>
> I'll try to find some time looking into it, but thought it might
> be a good idea to throw it out here in the mean time...

Seems like the only way to free dev->power.qos->latency_tolerance_req
is to call dev_pm_qos_update_user_latency_tolerance with a negative
val argument.  What an odd API..