[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230530093913.1656095-1-claudiu.beznea@microchip.com>
Date: Tue, 30 May 2023 12:39:05 +0300
From: Claudiu Beznea <claudiu.beznea@...rochip.com>
To: <mturquette@...libre.com>, <sboyd@...nel.org>,
<luca.ceresoli@...tlin.com>, <nm@...com>, <kristo@...nel.org>,
<ssantosh@...nel.org>, <michal.simek@...inx.com>
CC: <aford173@...il.com>, <mike.looijmans@...ic.nl>,
<robert.hancock@...ian.com>, <shawn.guo@...aro.org>,
<fabio.estevam@...escale.com>, <linux-clk@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-omap@...r.kernel.org>,
Claudiu Beznea <claudiu.beznea@...rochip.com>
Subject: [PATCH 0/8] clk: check memory returned by {devm_}kasprintf()
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
Powered by blists - more mailing lists