From: Nick Clifton <nickc@redhat.com>
To: jacob navia <jacob@jacob.remcomp.fr>, binutils@sourceware.org
Subject: Re: Possible Memory leak in bed hash.c
Date: Wed, 13 Sep 2023 11:47:43 +0100 [thread overview]
Message-ID: <fa9652ab-d746-a713-ddb5-c0415477b234@redhat.com> (raw)
In-Reply-To: <86B413C7-E812-411A-A790-90B80E81B411@jacob.remcomp.fr>
Hi Jacob,
> Priority: LOW
> In these times of plenty (gigabytes of RAM, etc) nobody cares about writing good software.
This is just a quick note to say that we do care.
We care about writing good code. We care about writing portable code.
We care about writing code that others will see, read and use, and we
hope, appreciate.
So please, do keep on filing bug reports and letting us know about problems,
but do not think that we do not care. We do.
Cheers
Nick
PS. Mind you the thing I do not care about are when I get a CVE report
for one of these memory leak bugs saying that the leak is a potential
source of a denial of service attack. I mean seriously, if one of the
binutils tools does not free all of its memory before exiting, can that
really be used as a DoS ?
prev parent reply other threads:[~2023-09-13 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 12:05 jacob navia
2023-09-13 6:37 ` Alan Modra
2023-09-13 10:39 ` Nick Clifton
2023-09-13 10:47 ` Nick Clifton [this message]
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=fa9652ab-d746-a713-ddb5-c0415477b234@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jacob@jacob.remcomp.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).