On Mon, Oct 21, 2024 at 12:25:08PM -0700, John Hubbard wrote: > On 10/21/24 10:23 AM, David Hildenbrand wrote: [snip] > > > > Just to raise it here: MADV_GUARD_INSTALL / MADV_GUARD_REMOVE or sth. > > > > like > > > > that would have been even clearer, at least to me. > > Yes, I think so. > > > > > > > :) > > > > > > It still feels like poisoning to me because we're explicitly putting > > > something in the page tables to make a range have different fault > > > behaviour > > > like a HW poisoning, and 'installing' suggests backing or something like > > > this, I think that's more confusing. > > > > I connect "poison" to "SIGBUS" and "corrupt memory state", not to "there is > > nothing and there must not be anything". Thus my thinking. But again, not > > the end of the world, just wanted to raise it ... > > "Poison" is used so far for fairly distinct things, and I'd very much like > to avoid extending its meaning to guard pages. It makes the other things > less unique, and it misses a naming and classification opportunity. > > "Guard" and "guard page" are fairly unique names. That's valuable. > > > thanks, > -- > John Hubbard >
Guys you're breaking my heart... Will you not leave me with even a remnant of a cultural reference?? [0] [0]:https://www.youtube.com/watch?v=_mej5wS7viw
