From: David Miller <davem@davemloft.net>
To: johan@kernel.org
Cc: f.fainelli@gmail.com, mugunthanvnm@ti.com,
yisen.zhuang@huawei.com, salil.mehta@huawei.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/4] net: ethernet: ti: cpsw: fix device and of_node leaks
Date: Tue, 01 Nov 2016 12:48:48 -0400 (EDT) [thread overview]
Message-ID: <20161101.124848.1812844488411463169.davem@davemloft.net> (raw)
In-Reply-To: <20161101164225.GC2664@localhost>
From: Johan Hovold <johan@kernel.org>
Date: Tue, 1 Nov 2016 17:42:25 +0100
> On Tue, Nov 01, 2016 at 12:27:11PM -0400, David Miller wrote:
>> From: Johan Hovold <johan@kernel.org>
>> Date: Tue, 1 Nov 2016 12:03:35 +0100
>>
>> > diff --git a/drivers/net/ethernet/ti/cpsw-phy-sel.c b/drivers/net/ethernet/ti/cpsw-phy-sel.c
>> > index 054a8dd23dae..589beb843f56 100644
>> > --- a/drivers/net/ethernet/ti/cpsw-phy-sel.c
>> > +++ b/drivers/net/ethernet/ti/cpsw-phy-sel.c
>> > @@ -176,8 +176,11 @@ void cpsw_phy_sel(struct device *dev, phy_interface_t phy_mode, int slave)
>> > }
>> >
>> > dev = bus_find_device(&platform_bus_type, NULL, node, match);
>> > + of_node_put(node);
>> > priv = dev_get_drvdata(dev);
>> >
>> > + put_device(dev);
>> > +
>> > priv->cpsw_phy_sel(priv, phy_mode, slave);
>> > }
>> > EXPORT_SYMBOL_GPL(cpsw_phy_sel);
>>
>> The only reference you have to 'dev' is the one obtained from the
>> bus_find_device() call, therefore you must at least hold onto
>> 'dev' until after the priv->cpsw_phy_sel(priv, phy_mode, slave); call.
>
> As I mentioned in the commit message "...there is no guarantee that the
> devres-managed struct cpsw_phy_sel_priv will continue to be valid until
> this function returns regardless of this change".
>
> Specifically, holding a reference to dev does not prevent the
> cpsw_phy_sel driver from being unbound and priv from being freed.
But you should at least hold onto the object while you call a function
pointer embedded in a data structure referred by it.
next prev parent reply other threads:[~2016-11-01 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 11:03 [PATCH net 0/4] net: fix device reference leaks Johan Hovold
2016-11-01 11:03 ` [PATCH net 1/4] phy: " Johan Hovold
2016-11-01 11:03 ` [PATCH net 2/4] net: ethernet: ti: cpsw: fix device and of_node leaks Johan Hovold
2016-11-01 16:27 ` David Miller
2016-11-01 16:42 ` Johan Hovold
2016-11-01 16:48 ` David Miller [this message]
2016-11-01 17:04 ` Johan Hovold
2016-11-01 11:03 ` [PATCH net 3/4] net: ethernet: ti: davinci_emac: fix device reference leak Johan Hovold
2016-11-01 11:03 ` [PATCH net 4/4] net: hns: fix device reference leaks Johan Hovold
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=20161101.124848.1812844488411463169.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@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).