From: Dan Carpenter <dan.carpenter@oracle.com>
To: gmbnomis@gmail.com
Cc: Richard Weinberger <richard@nod.at>, linux-mtd@lists.infradead.org
Subject: [bug report] ARM: Orion: fix driver probe error handling with respect to clk
Date: Mon, 6 Feb 2017 18:29:47 +0300 [thread overview]
Message-ID: <20170206152947.GA17091@mwanda> (raw)
Hello Simon Baatz,
The patch baffab28b131: "ARM: Orion: fix driver probe error handling
with respect to clk" from Jul 19, 2012, leads to the following static
checker warning:
drivers/mtd/nand/orion_nand.c:172 orion_nand_probe()
warn: 'clk' was already freed.
drivers/mtd/nand/orion_nand.c
150 /* Not all platforms can gate the clock, so it is not
151 an error if the clock does not exists. */
152 clk = clk_get(&pdev->dev, NULL);
153 if (!IS_ERR(clk)) {
154 clk_prepare_enable(clk);
155 clk_put(clk);
Huh? Apparently clk_get() and clk_put() are not ref counted
opperations?
You would think they would be from the name. What it looks like to me
is that clk_put() should be renamed clk_free(). The comments on
clk_put() are not totally clear on this. I'm just joking. :P There
aren't any comments...
156 }
157
158 ret = nand_scan(mtd, 1);
159 if (ret)
160 goto no_dev;
161
162 mtd->name = "orion_nand";
163 ret = mtd_device_register(mtd, board->parts, board->nr_parts);
164 if (ret) {
165 nand_release(mtd);
166 goto no_dev;
167 }
168
169 return 0;
170
171 no_dev:
172 if (!IS_ERR(clk)) {
173 clk_disable_unprepare(clk);
Any later reference to "clk" after clk_put() is a use after free.
174 clk_put(clk);
175 }
176
177 return ret;
178 }
regards,
dan carpenter
next reply other threads:[~2017-02-06 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 15:29 Dan Carpenter [this message]
2017-02-06 23:38 ` [bug report] ARM: Orion: fix driver probe error handling with respect to clk Simon Baatz
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=20170206152947.GA17091@mwanda \
--to=dan.carpenter@oracle.com \
--cc=gmbnomis@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.