From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
Richard Earnshaw via Libc-alpha <libc-alpha@sourceware.org>
Cc: Richard Earnshaw <rearnsha@arm.com>
Subject: Re: [PATCH v5 0/6] [committed] Memory tagging support
Date: Tue, 22 Dec 2020 18:28:00 +0530 [thread overview]
Message-ID: <c431e725-0145-8be6-96f2-7797b0b61a3b@gotplt.org> (raw)
In-Reply-To: <87mty6gg53.fsf@igel.home>
On 12/22/20 6:19 PM, Andreas Schwab wrote:
> This breaks everything. I'm getting "realloc(): invalid next size" all
> over the place.
On arm64 or on x86_64? Also, which tests is it breaking and with what
configuration? I haven't seen any failures with --prefix=/usr or with
--enable-memory-tagging on x86_64. I trust Szabolcs/Richard tested arm64.
Siddhesh
next prev parent reply other threads:[~2020-12-22 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 15:33 Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 1/6] config: Allow memory tagging to be enabled when configuring glibc Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 2/6] elf: Add a tunable to control use of tagged memory Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 3/6] malloc: Basic support for memory tagging in the malloc() family Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 4/6] linux: Add compatibility definitions to sys/prctl.h for MTE Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 5/6] aarch64: Add sysv specific enabling code for memory tagging Richard Earnshaw
2020-12-21 15:33 ` [PATCH v5 6/6] aarch64: Add aarch64-specific files for memory tagging support Richard Earnshaw
2020-12-22 12:49 ` [PATCH v5 0/6] [committed] Memory " Andreas Schwab
2020-12-22 12:58 ` Siddhesh Poyarekar [this message]
2020-12-22 13:21 ` Andreas Schwab
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=c431e725-0145-8be6-96f2-7797b0b61a3b@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=libc-alpha@sourceware.org \
--cc=rearnsha@arm.com \
--cc=schwab@linux-m68k.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).