From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: elseifthen@gmx.com Subject: Re: [PATCH 3/4] logger: fix memory leaks [asan] To: Karel Zak , Sami Kerola References: <20170911195717.817-1-kerolasa@iki.fi> <20170911195717.817-3-kerolasa@iki.fi> <20170915110547.7znrzkpd7wf3mmdq@ws.net.home> Cc: util-linux@vger.kernel.org From: J William Piggott Message-ID: Date: Fri, 15 Sep 2017 20:54:41 -0400 MIME-Version: 1.0 In-Reply-To: <20170915110547.7znrzkpd7wf3mmdq@ws.net.home> Content-Type: text/plain; charset=windows-1252 List-ID: On 09/15/2017 07:05 AM, Karel Zak wrote: > On Mon, Sep 11, 2017 at 08:57:16PM +0100, Sami Kerola wrote: 8< --- > The mem-leaks are bad thing in daemons, libs, libs tests, and > allocation in loop is dangerous, otherwise for command line utils you > waste time with this kind of free() calls, because kernel on exit() > will be faster to remove all the program from memory. Does this rule apply to the free() calls in hwclock.c? > > Karel >