From: Greg KH <gregkh@linuxfoundation.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: chunfeng.yun@mediatek.com, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: roles: fix of node refcount leak in usb_role_switch_is_parent()
Date: Fri, 18 Nov 2022 18:57:54 +0100 [thread overview]
Message-ID: <Y3fHom6pvHT+dD5k@kroah.com> (raw)
In-Reply-To: <20221118141850.806564-1-yangyingliang@huawei.com>
On Fri, Nov 18, 2022 at 10:18:50PM +0800, Yang Yingliang wrote:
> I got the following report:
>
> OF: ERROR: memory leak, expected refcount 1 instead of 2,
> of_node_get()/of_node_put() unbalanced - destroy cset entry:
> attach overlay node /i2c/pmic@34
report from what? What generates this?
next prev parent reply other threads:[~2022-11-18 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 14:18 [PATCH] usb: roles: fix of node refcount leak in usb_role_switch_is_parent() Yang Yingliang
2022-11-18 17:57 ` Greg KH [this message]
2022-11-19 7:47 ` Yang Yingliang
2022-11-19 8:51 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y3fHom6pvHT+dD5k@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chunfeng.yun@mediatek.com \
--cc=linux-usb@vger.kernel.org \
--cc=yangyingliang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).