On 2021-08-13 14:54, Dan Carpenter wrote:
On Fri, Aug 13, 2021 at 01:55:38PM +0100, Robin Murphy wrote:
On 2021-08-13 12:33, Dan Carpenter wrote:
If devm_regulator_get_optional() returns an error pointer, then we
should return it to the user. The current code makes an exception
for -ENODEV that will result in an error pointer dereference on the
next line when it calls regulator_enable(). Remove the exception.
Doesn't this break the apparent intent of the regulator being optional,
though?
Argh... Crap. My patch is wrong, but the bug is real.
Yeah, I guess this probably wants to follow the same pattern as
rockchip_pcie_set_vpcie() in the older driver, where it's the regulator
API calls which get wrapped in checks.
This code should follow the standard kernel idiom of returning error
pointers when there are errors and returning NULL when an optional
feature is disabled. The problem with returning a Special Error code
to mean "disabled" is that someone will use the Special Error code to
mean an error.
And that has already sort of happened, because _regulator_get() returns
-ENODEV which would will cause the Oops I described in my patch.
Ugh... The correct thing is to convert it to NULL/error pointers. I
have not looked at how hard that is though...
Indeed I've thought before that it would be nice if regulators worked
like GPIOs, where the absence of an optional one does give you NULL, and
most of the API is also NULL-safe. Probably a pretty big job though...
Thanks,
Robin.
