From: J William Piggott <elseifthen@gmx.com>
To: Karel Zak <kzak@redhat.com>, Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 3/4] logger: fix memory leaks [asan]
Date: Fri, 15 Sep 2017 20:54:41 -0400 [thread overview]
Message-ID: <c51ca22c-801a-1711-144a-aba8d008bb18@gmx.com> (raw)
In-Reply-To: <20170915110547.7znrzkpd7wf3mmdq@ws.net.home>
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
>
next prev parent reply other threads:[~2017-09-16 0:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 19:57 [PATCH 1/4] uuidparse: fix stack-buffer-overflow [asan] Sami Kerola
2017-09-11 19:57 ` [PATCH 2/4] libsmartcols: fix heap-buffer-overflow [asan] Sami Kerola
2017-09-15 11:47 ` Karel Zak
2017-09-11 19:57 ` [PATCH 3/4] logger: fix memory leaks [asan] Sami Kerola
2017-09-15 11:05 ` Karel Zak
2017-09-16 0:54 ` J William Piggott [this message]
2017-09-16 7:31 ` Sami Kerola
2017-09-18 8:55 ` Karel Zak
2017-09-18 9:40 ` Karel Zak
2017-09-11 19:57 ` [PATCH 4/4] partx: fix memory leak [asan] Sami Kerola
2017-09-15 11:33 ` [PATCH 1/4] uuidparse: fix stack-buffer-overflow [asan] Karel Zak
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=c51ca22c-801a-1711-144a-aba8d008bb18@gmx.com \
--to=elseifthen@gmx.com \
--cc=kerolasa@iki.fi \
--cc=kzak@redhat.com \
--cc=util-linux@vger.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