From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
libc-alpha@sourceware.org, carlos@redhat.com
Subject: Re: [RFC] Supporting malloc_usable_size
Date: Fri, 02 Dec 2022 13:39:45 +0100 [thread overview]
Message-ID: <87pmd2rnce.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87o7smrnlh.fsf@igel.home> (Andreas Schwab's message of "Fri, 02 Dec 2022 13:34:18 +0100")
* Andreas Schwab:
> On Dez 02 2022, Siddhesh Poyarekar wrote:
>
>> However the man page starts with "Although the excess bytes can be
>> overwritten by the application without ill effects" and maybe that
>> reassurance needs to be dropped.
>
> Or perhaps amended: "until the next call to malloc/realloc/free in any
> thread".
The list will never be complete because glibc can call into the malloc
subsystem internally, or even spontaneously from an internal service
thread.
Thanks,
Florian
next prev parent reply other threads:[~2022-12-02 12:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 21:32 Siddhesh Poyarekar
2022-12-02 4:42 ` DJ Delorie
2022-12-02 5:00 ` Sam James
2022-12-02 5:28 ` DJ Delorie
2022-12-02 12:36 ` Siddhesh Poyarekar
2022-12-02 19:16 ` DJ Delorie
2022-12-02 19:49 ` Siddhesh Poyarekar
2022-12-02 19:57 ` DJ Delorie
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 [this message]
2022-12-05 18:46 ` Zack Weinberg
2022-12-05 19:04 ` Siddhesh Poyarekar
2022-12-05 20:35 ` Florian Weimer
2022-12-06 19:25 ` Siddhesh Poyarekar
2022-12-07 10:01 ` Florian Weimer
2022-12-07 16:34 ` Siddhesh Poyarekar
2022-12-07 16:54 ` Adhemerval Zanella Netto
2022-12-07 16:57 ` Sam James
2022-12-07 17:39 ` Florian Weimer
2022-12-09 15:42 ` Siddhesh Poyarekar
2022-12-07 18:45 ` DJ Delorie
2022-12-02 12:54 ` Florian Weimer
2022-12-02 13:54 Wilco Dijkstra
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=87pmd2rnce.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.org \
--cc=siddhesh@gotplt.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).