linux-kernel - Re: [PATCH] clocksource/drivers/timer-atmel-pit: properly handle error cases

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 27 Sep 2018 12:00:35 +0200
From:   Daniel Lezcano <daniel.lezcano@...aro.org>
To:     Nicolas Ferre <nicolas.ferre@...rochip.com>
Cc:     Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Boris Brezillon <boris.brezillon@...tlin.com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Cristian Birsan <Cristian.Birsan@...rochip.com>
Subject: Re: [PATCH] clocksource/drivers/timer-atmel-pit: properly handle
 error cases

On 26/09/2018 14:38, Nicolas Ferre wrote:
> Daniel,
> 
> On 01/05/2018 at 10:36, Daniel Lezcano wrote:
>> On Wed, Apr 25, 2018 at 12:14:39PM +0200, Alexandre Belloni wrote:
>>> smatch now reports a possible leak:
>>>
>>> smatch warnings:
>>> drivers/clocksource/timer-atmel-pit.c:183 at91sam926x_pit_dt_init()
>>> warn: possible memory leak of 'data'
>>>
>>> Ensure data is freed before exiting with an error.
>>>
>>> Reported-by: Dan Carpenter <dan.carpenter@...cle.com>
>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@...tlin.com>
>>> ---
>>
>> Applied for 4.17-rc
> 
> We don't see it in Mainline as of 4.19-rc neither in linux-next. Has it
> been forgotten?

Yes, my bad. I thought it was merge in tip:timers/urgent

Let me resend another PR for 4.19-rc and Cc stable@




-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog