From: Stefan Jumarea <firstname.lastname@example.org>
Cc: email@example.com, Razvan Deaconescu <firstname.lastname@example.org>,
Michalis Pappas <email@example.com>
Subject: [musl] Project Proposal MTE Support
Date: Wed, 19 Jul 2023 10:37:06 +0300 [thread overview]
Message-ID: <ZLeSohZHT2xHA/xx@stefan-IdeaPad-5-15ARE05> (raw)
With the present, I would like to discuss the prospect of adding MTE support in
the Musl memory allocator.
Currently, (starting with release 1.2.1, August 2020, commit 503bd3976623), Musl
introduces a new "malloc" implementation ("mallocng"), which solves a lot of the
intended malloc-hardening issues. However, further hardening can be implemented,
including MTE (Memory Tagging Extension) support.
We are using Musl as the primary libc within Unikraft, a Unikernel Developing Kit,
and we support MTE on the low-level memory allocator. This however lacks a lot in
terms of granularity, as the internal allocator has a page-size minimum allocation
level, and tagging one page at the time still allows for memory safety violations
in the area of one page.
Our goal is to have MTE protection implemented in a fine-grained allocator
(i.e. Musl "malloc" implementation), that will successfully prevent memory safety
Extended measurements will need to be done in order to provide a clear overview
over the performance impact that using MTE will have, but the architecture
provides ways to optimize the implementation for functions like "calloc" or
large "malloc" blocks (instructions like "store allocation tag with zeroing",
"sdgz", "store allocation tag for blocks", "sdgm"), along with an asynchronous
way to check for a Tag Check Fault (e.g. on IRQs, on task / thread switches, etc.).
A bit about myself, my name is Ștefan Jumărea, I am an undergraduate student in
the final year at University Politehnica of Bucharest, and I’ve been part of the
Unikraft OSS project for almost two years.
I would like to make this my diploma project (due June 2024).
Is it something of interest in the Musl community?
Is it planned work, is there anyone else working on it? If not, I would like to
start working on the project in the next weeks.
Do you have any comments, suggestions, or other things I should consider?
next reply other threads:[~2023-07-19 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 7:37 Stefan Jumarea [this message]
2023-07-20 1:51 ` Rich Felker
2023-07-20 5:47 ` Stefan Jumarea
2023-07-20 13:03 ` Szabolcs Nagy
2023-07-20 19:02 ` Rich Felker
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 NNTP newsgroup(s).