zlacker

[parent] [thread] 4 comments
1. y1n0+(OP)[view] [source] 2024-10-11 04:59:35
There are more 4k boundaries than 16k boundaries. The issue is code compiled for 4k boundaries running on a 16k system.
replies(1): >>amoss+h7
2. amoss+h7[view] [source] 2024-10-11 06:22:42
>>y1n0+(OP)
I'm missing something here. Assuming there are pages at 0k, 16k, 32k etc - all of those pages are aligned on 4k boundaries as 4k > 16k. So code written with the assumption that its pages are 4k aligned should have that assumption met when running with 16k pages. It is still early here and I have only had one cup of coffee. Am I misunderstanding something really obvious?
replies(1): >>dezgeg+sa
◧◩
3. dezgeg+sa[view] [source] [discussion] 2024-10-11 06:54:49
>>amoss+h7
x86 app might mmap 8kb, then munmap the second 4kb and expect that to work. But not possible on 16k pages.
replies(1): >>amoss+Ad
◧◩◪
4. amoss+Ad[view] [source] [discussion] 2024-10-11 07:28:59
>>dezgeg+sa
ah ok, so it would not be pointer alignment inside the pages but instead the assumption that page +4k is a page.
replies(1): >>MBCook+ca1
◧◩◪◨
5. MBCook+ca1[view] [source] [discussion] 2024-10-11 16:14:37
>>amoss+Ad
I was a little confused by that in the article as well. It being a granularity issue makes more sense to me.
[go to top]