On Tue, 20 Jun 2017 21:45:31 -0700 stan <stanl-fedorauser@xxxxxxxxxxx> wrote: > On Tue, 20 Jun 2017 23:44:24 -0400 > Tony Nelson <tonynelson@xxxxxxxxxxxxxxxxx> wrote: > > > It's not allocated memory. It's a Page Table Entry in the Kernel > > that ensures that no actual memory is mapped there and that the > > region is thus unreadable and unwritable. This is not unlike a > > swapped-out page, except the Kernel Page Table Entry for such a > > page says that it can be swapped back in and from what > > (memory-mapped) file. So all it uses is address space and Page > > Table Entries. > > Thanks. I had wondered if they did that. But, given that, why restrict the guard buffer to 4kB? Since it is virtual, why not make it 100 MB, or on 64 bit systems, 100 GB? All for the same price, a little pointer indirection, and pushes the likelihood of the stack clash problem to nil or close. I think it would be cheaper than the stack-check solution, as well. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
