Created attachment 158323 [details] memguard_cursor patch With MG_GUARD_AROUND option, memguard increases memguard_cursor with one more PAGE_SIZE. This results in one PAGE_SIZE fragment in KVA. * before patch old memguard_cursor: 0xfffffe0000400000 memeguard:allocate 0x3000 next memguard_curor: 0xfffffe0000404000 * after patch old memguard_cursor: 0xfffffe0000400000 memeguard:allocate 0x3000 next memguard_curor: 0xfffffe0000403000
I think this is intentional.
(In reply to Conrad E. Meyer from comment #1) Indeed, this is _the_ implementation of the guard page, it seems.