netdev - Re: [PATCH v2 net-next] net: phy: adjust fixed_phy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20141007.130233.354860766225253280.davem@davemloft.net>
Date:	Tue, 07 Oct 2014 13:02:33 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	pgynther@...gle.com
Cc:	netdev@...r.kernel.org, f.fainelli@...il.com,
	thomas.petazzoni@...e-electrons.com
Subject: Re: [PATCH v2 net-next] net: phy: adjust fixed_phy_register()
 return value

From: Petri Gynther <pgynther@...gle.com>
Date: Tue, 7 Oct 2014 09:47:37 -0700

> I'm not sure if I understand your comment. The caller of
> fixed_phy_register() now gets the pointer to the phydev created by
> get_phy_device(). What other thread is aware of this pointer and how could
> they free it? Isn't the caller of fixed_phy_register() exclusively in
> charge of the created phydev?

If this is the case then my concerns are unfounded.

Thanks for clearing that up and I'll apply your patch, thanks!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html