From: "Vitaly Cheptsov" <vit9696@protonmail.com>
To: Pedro Falcato <pedro.falcato@gmail.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] Question about UEFI, AddressSanitizer and MMU mappings
Date: Sat, 26 Mar 2022 11:30:48 -0700 [thread overview]
Message-ID: <20985.1648319448324224181@groups.io> (raw)
In-Reply-To: <CAKbZUD0muto-TtfhYK3PUoLMnBo416232EhBabNusNzr8EU1sg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
Hello,
I have some experience porting LLVM Sanitizers and am very interested in this project coming live to UEFI as well. I had success with both entirely static shadow memory allocation and dynamic on-demand allocation. For ASan in the UEFI my personal idea would be trying to avoid page-fault allocation of the shadow memory, but rather adapting the allocators to not only allocate the "origin" memory but also "shadow memory" with a known shift and base (which are configurable now).
The parts that seem difficult to me are concurrency and trying to make ASan work in whitelist mode (i.e. forbidding all accesses that are not greenlighted), but otherwise it should be rather straight-forward if we do not include fake stack in the task and focus on DXE at first. All in all, I can be a co-mentor in this task and am ready to help as needed.
Best wishes,
Vitaly
[-- Attachment #2: Type: text/html, Size: 913 bytes --]
next prev parent reply other threads:[~2022-03-26 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 22:32 Question about UEFI, AddressSanitizer and MMU mappings Pedro Falcato
2022-03-25 9:07 ` [edk2-devel] " Marvin Häuser
2022-03-25 18:42 ` Andrew Fish
2022-03-25 20:47 ` Pedro Falcato
2022-03-26 18:30 ` Vitaly Cheptsov [this message]
2022-03-28 11:32 ` Steven Shi
2022-03-28 16:30 ` Pedro Falcato
2022-03-29 11:58 ` Steven Shi
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-list 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=20985.1648319448324224181@groups.io \
--to=devel@edk2.groups.io \
/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