All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org
Subject: re: PM / OPP: Add OPP sharing information to OPP library
Date: Mon, 10 Aug 2015 19:40:09 +0300	[thread overview]
Message-ID: <20150810164009.GB10496@mwanda> (raw)

Hello Viresh Kumar,

The patch 064416586190: "PM / OPP: Add OPP sharing information to OPP
library" from Jul 29, 2015, leads to the following static checker
warning:

	drivers/base/power/opp.c:1341 _of_init_opp_table_v2()
	error: 'dev_opp' dereferencing possible ERR_PTR()

drivers/base/power/opp.c
  1328          }
  1329  
  1330          /* There should be one of more OPP defined */
  1331          if (WARN_ON(!count))
  1332                  goto put_opp_np;

Should we set "ret" here?

  1333  
  1334          if (!ret) {
  1335                  if (!dev_opp) {
                             ^^^^^^^
No need to test this, we tested at the start of the function.

  1336                          dev_opp = _find_device_opp(dev);
  1337                          if (WARN_ON(!dev_opp))

This should be checking for IS_ERR().  We probably want to set "ret =
PTR_ERR(dev_opp) as well.

  1338                                  goto put_opp_np;
  1339                  }
  1340  
  1341                  dev_opp->np = opp_np;
  1342                  dev_opp->shared_opp = of_property_read_bool(opp_np,
  1343                                                              "opp-shared");
  1344          } else {
  1345                  of_free_opp_table(dev);
  1346          }
  1347  
  1348  put_opp_np:
  1349          of_node_put(opp_np);
  1350  
  1351          return ret;
  1352  }

Checking for "!ret" on line 1334 is "success handling" style code.
Success handling leads to multiple indent levels and is more twisted and
confusing.  I generally prefer to keep my error handling paths separate
from the success path although in this case we call of_node_put() on
both paths, so maybe a shared exit path makes sense.

To me boils down to a question of, "How much is shared and how much is
different.  Also should we call of_free_opp_table() if _find_device_opp()
fails?"  If not then I would use a common exit path, otherwise I would
split them apart.

Shared:

	if (ret) {
		of_free_opp_table(dev);
		goto put_opp_npl;
	}

	dev_opp = _find_device_opp(dev);
	if (WARN_ON(IS_ERR(dev_opp))) {
		ret = PTR_ERR(dev_opp);
		goto put_opp_np;
	}

	dev_opp->np = opp_np;
	dev_opp->shared_opp = of_property_read_bool(opp_np, "opp-shared");

put_opp_np:
	of_node_put(opp_np);
	return ret;

Split apart:

	if (ret)
		goto free_opp_table;

	dev_opp = _find_device_opp(dev);
	if (WARN_ON(IS_ERR(dev_opp))) {
		ret = PTR_ERR(dev_opp);
		goto free_opp_table;
	}

	dev_opp->np = opp_np;
	dev_opp->shared_opp = of_property_read_bool(opp_np, "opp-shared");

	of_node_put(opp_np);
	return 0;

free_opp_table:
	of_free_opp_table(dev);
put_opp_np:
	of_node_put(opp_np);
	return ret;

regards,
dan carpenter

             reply	other threads:[~2015-08-10 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 16:40 Dan Carpenter [this message]
2015-08-11  8:22 ` PM / OPP: Add OPP sharing information to OPP library Viresh Kumar

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=20150810164009.GB10496@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=viresh.kumar@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.