From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<luca.ceresoli@bootlin.com>, <nm@ti.com>, <kristo@kernel.org>,
<ssantosh@kernel.org>, <michal.simek@xilinx.com>
Cc: <aford173@gmail.com>, <mike.looijmans@topic.nl>,
<robert.hancock@calian.com>, <shawn.guo@linaro.org>,
<fabio.estevam@freescale.com>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: [PATCH 0/8] clk: check memory returned by {devm_}kasprintf()
Date: Tue, 30 May 2023 12:39:05 +0300 [thread overview]
Message-ID: <20230530093913.1656095-1-claudiu.beznea@microchip.com> (raw)
Hi,
While browsing some code I noticed that there are places where pointer
returned by devm_kasprintf() or kasprintf() is not checked. Thus I've
tooked the chance and fixed this (by updating kmerr.cocci script,
changes published at [1]). Along with it some other places where
resources may need to be freed on failure paths were updated.
Thank you,
Claudiu Beznea
[1] https://lore.kernel.org/all/20230530074044.1603426-1-claudiu.beznea@microchip.com/
Claudiu Beznea (8):
clk: vc5: check memory returned by kasprintf()
clk: cdce925: check return value of kasprintf()
clk: si5341: return error if one synth clock registration fails
clk: si5341: check return value of {devm_}kasprintf()
clk: si5341: free unused memory on probe failure
clk: keystone: sci-clk: check return value of kasprintf()
clk: ti: clkctrl: check return value of kasprintf()
clk: clocking-wizard: check return value of devm_kasprintf()
drivers/clk/clk-cdce925.c | 12 +++++++
drivers/clk/clk-si5341.c | 38 +++++++++++++---------
drivers/clk/clk-versaclock5.c | 29 +++++++++++++++++
drivers/clk/keystone/sci-clk.c | 2 ++
drivers/clk/ti/clkctrl.c | 7 ++++
drivers/clk/xilinx/clk-xlnx-clock-wizard.c | 5 +++
6 files changed, 78 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2023-05-30 9:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 9:39 Claudiu Beznea [this message]
2023-05-30 9:39 ` [PATCH 1/8] clk: vc5: check memory returned by kasprintf() Claudiu Beznea
2023-05-31 16:32 ` Luca Ceresoli
2023-06-20 18:53 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 2/8] clk: cdce925: check return value of kasprintf() Claudiu Beznea
2023-06-20 18:54 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 3/8] clk: si5341: return error if one synth clock registration fails Claudiu Beznea
2023-06-20 18:54 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 4/8] clk: si5341: check return value of {devm_}kasprintf() Claudiu Beznea
2023-06-20 18:54 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 5/8] clk: si5341: free unused memory on probe failure Claudiu Beznea
2023-06-20 18:55 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 6/8] clk: keystone: sci-clk: check return value of kasprintf() Claudiu Beznea
2023-05-31 4:12 ` Tony Lindgren
2023-06-20 18:55 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 7/8] clk: ti: clkctrl: " Claudiu Beznea
2023-05-31 4:12 ` Tony Lindgren
2023-06-20 18:55 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 8/8] clk: clocking-wizard: check return value of devm_kasprintf() Claudiu Beznea
2023-06-20 18:55 ` Stephen Boyd
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=20230530093913.1656095-1-claudiu.beznea@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=aford173@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@xilinx.com \
--cc=mike.looijmans@topic.nl \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=robert.hancock@calian.com \
--cc=sboyd@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=ssantosh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).