[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c540ead8-0d05-86d8-681c-9003600355ce@huawei.com>
Date: Tue, 1 Dec 2020 09:23:00 +0800
From: Qinglang Miao <miaoqinglang@...wei.com>
To: Bartosz Golaszewski <bgolaszewski@...libre.com>
CC: Linus Walleij <linus.walleij@...aro.org>,
Michal Simek <michal.simek@...inx.com>,
linux-gpio <linux-gpio@...r.kernel.org>,
arm-soc <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio: zynq: fix reference leak in zynq_gpio functions
在 2020/12/1 0:44, Bartosz Golaszewski 写道:
> On Fri, Nov 27, 2020 at 10:40 AM Qinglang Miao <miaoqinglang@...wei.com> wrote:
>>
>> pm_runtime_get_sync will increment pm usage counter even it
>> failed. Forgetting to putting operation will result in a
>> reference leak here.
>>
>> A new function pm_runtime_resume_and_get is introduced in
>> [0] to keep usage counter balanced. So We fix the reference
>> leak by replacing it with new funtion.
>>
>> [0] dd8088d5a896 ("PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter")
>
> Is this upstream yet?
>
> Bartosz
> .
Yep, it's introduced in v5.10-rc5
>
Powered by blists - more mailing lists