From: Sam James via Libc-alpha <libc-alpha@sourceware.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Florian Weimer <fweimer@redhat.com>,
Zack Weinberg via Libc-alpha <libc-alpha@sourceware.org>,
Zack Weinberg <zack@owlfolio.org>, DJ Delorie <dj@redhat.com>
Subject: Re: [RFC] Supporting malloc_usable_size
Date: Wed, 7 Dec 2022 16:57:12 +0000 [thread overview]
Message-ID: <538832AC-4ED6-41CF-A655-22F691ADA88C@gentoo.org> (raw)
In-Reply-To: <f648dde2-88a6-21f5-7b8c-548368837317@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
> On 7 Dec 2022, at 16:54, Adhemerval Zanella Netto via Libc-alpha <libc-alpha@sourceware.org> wrote:
> [snip]
> I tend to agree with full deprecation, systemd MALLOC_SIZEOF_SAFE is an
> example of what user needs to hack around with an ill defined interface and
> _FORTIFY_SOURCE=3 warning should be clear that keep it is not a gain in long
> term (besides adding even more trouble for portability).
>
> Another possibility would to make malloc_usable_size always return the malloc
> size argument (although it would add some internal metadata costs).
My position is already clear (full deprecation), but if someone does feel
it's useful fo them, they can always speak up over the lengthy
deprecation period anyway. It could always be reversed if necessary.
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2022-12-07 16:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 21:32 [RFC] Supporting malloc_usable_size Siddhesh Poyarekar
2022-12-02 4:42 ` DJ Delorie via Libc-alpha
2022-12-02 5:00 ` Sam James via Libc-alpha
2022-12-02 5:28 ` DJ Delorie via Libc-alpha
2022-12-02 12:36 ` Siddhesh Poyarekar
2022-12-02 19:16 ` DJ Delorie via Libc-alpha
2022-12-02 19:49 ` Siddhesh Poyarekar
2022-12-02 19:57 ` DJ Delorie via Libc-alpha
2022-12-02 12:03 ` Andreas Schwab
2022-12-02 12:22 ` Siddhesh Poyarekar
2022-12-02 12:34 ` Andreas Schwab
2022-12-02 12:39 ` Florian Weimer via Libc-alpha
2022-12-05 18:46 ` Zack Weinberg via Libc-alpha
2022-12-05 19:04 ` Siddhesh Poyarekar
2022-12-05 20:35 ` Florian Weimer via Libc-alpha
2022-12-06 19:25 ` Siddhesh Poyarekar
2022-12-07 10:01 ` Florian Weimer via Libc-alpha
2022-12-07 16:34 ` Siddhesh Poyarekar
2022-12-07 16:54 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-07 16:57 ` Sam James via Libc-alpha [this message]
2022-12-07 17:39 ` Florian Weimer via Libc-alpha
2022-12-09 15:42 ` Siddhesh Poyarekar
2022-12-07 18:45 ` DJ Delorie via Libc-alpha
2022-12-02 12:54 ` Florian Weimer via Libc-alpha
-- strict thread matches above, loose matches on Subject: below --
2022-12-02 13:54 Wilco Dijkstra via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=538832AC-4ED6-41CF-A655-22F691ADA88C@gentoo.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=sam@gentoo.org \
--cc=siddhesh@gotplt.org \
--cc=zack@owlfolio.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).