Skip to content

Strange behavior of MemEngine.map. #69

Answered by Boyan-MILANOV
Rubonnek asked this question in Q&A
Discussion options

You must be logged in to vote

Hey!

there's no mention of MemEngine.map which is necessary to run MemEngine.write against a certain address

I agree that it wouldn't hurt mentioning the map() method there :)

There's also a strange behavior with this map call -- is the following expected?
[...]
It doesn't error out. I was expecting I would get an invalid memory write/read at any address other than 0x100, but I only get an error after trying to read over the 0xfff range.

It's expected. Maat manages memory access permissions at the page level, just like operating systems do. And the default page size is 0x1000. So when requesting a mapping that is smaller than a page, or overlaps between pages, Maat will always map the…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Rubonnek
Comment options

Answer selected by Rubonnek
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants