[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37ff7ca4-dc7c-6a43-94a3-9628efe69b25@web.de>
Date: Wed, 24 Jun 2020 12:06:35 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Tiezhu Yang <yangtiezhu@...ngson.cn>, devicetree@...r.kernel.org,
linux-mips@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Huacai Chen <chenhc@...ote.com>,
Jason Cooper <jason@...edaemon.net>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Marc Zyngier <maz@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Xuefeng Li <lixuefeng@...ngson.cn>
Subject: Re: [1/7] irqchip: Fix potential resource leaks
>> Were any known software analysis tools involved for the detection of
>> questionable source code places?
>
> kmemleak can detect memory leak,
> but I do not know how to detect other kind of leaks.
How do you think about to extend source code analysis tools accordingly?
> I think consciously release resource in the error path can avoid leaks.
Is it often too easy to overlook relevant function calls?
Regards,
Markus
Powered by blists - more mailing lists