mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <>
Cc: Johannes Zink <>,
	Ahmad Fatoum <>
Subject: [PATCH master 1/2] regulator: handle regulator_get_voltage(NULL) gracefully
Date: Mon, 18 Jul 2022 13:48:23 +0200	[thread overview]
Message-ID: <> (raw)

Unlike recent versions of Linux, barebox represents the dummy regulator
as a NULL pointer and regulator API is supposed to anticipate operation
on a NULL pointer. When regulator_get_voltage was ported from Linux,
this was not taken into consideration, which leads to
regulator_get_voltage(NULL) crashing with a NULL pointer dereference.

Fix this by returning -EINVAL for dummy regulators. This aligns us with
how Linux would behave in this situation.

Fixes: 6ee83ce08b24 ("regulator: add regulator_get_voltage() to API")
Reported-by: Johannes Zink <>
Signed-off-by: Ahmad Fatoum <>
 drivers/regulator/core.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 1fb344656f38..472b26f3a0ac 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -574,9 +574,14 @@ EXPORT_SYMBOL_GPL(regulator_bulk_free);
 int regulator_get_voltage(struct regulator *regulator)
-	struct regulator_dev *rdev = regulator->ri->rdev;
+	struct regulator_dev *rdev;
 	int sel, ret;
+	if (!regulator)
+		return -EINVAL;
+	rdev = regulator->ri->rdev;
 	if (rdev->desc->ops->get_voltage_sel) {
 		sel = rdev->desc->ops->get_voltage_sel(rdev);
 		if (sel < 0)

             reply	other threads:[~2022-07-18 11:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 11:48 Ahmad Fatoum [this message]
2022-07-18 11:48 ` [PATCH master 2/2] common: don't fixup empty serial/machine_compatible strings Ahmad Fatoum
2022-08-08 14:21 ` [PATCH master 1/2] regulator: handle regulator_get_voltage(NULL) gracefully Sascha Hauer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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