linux-kernel - Re: [PATCH 1/2] regulator: gpio: Avoid unnecessarily copying data structures in probe()

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1aPBrU-0000QT-G3@stardust.g4.wien.funkfeuer.at>
Date:	Fri, 29 Jan 2016 17:25:28 +0100
From:	Harald Geyer <harald@...ib.org>
To:	Mark Brown <broonie@...nel.org>
cc:	Harald Geyer <harald@...ib.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Heiko Stuebner <heiko@...ech.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] regulator: gpio: Avoid unnecessarily copying data structures in probe()

Mark Brown writes:
> On Thu, Jan 28, 2016 at 07:55:17PM +0000, Harald Geyer wrote:
> > The data structures either have been copied in
> > of_get_gpio_regulator_config() already or are part of platform data,
> > which we keep a pointer to for the life time of the device anyway.
> 
> The point of this code is to avoid referring to platform data after
> probe for robustness.

Well, if we can't rely on platform data staying available after probe()
then probably we shouldn't keep a pointer to it - but thats a different
issue, so lets focus on the original problem:

What's your preferred way to fix the error path of probe() then?

Harald