> I had noticed that MADV_DONTFORK can result in different behavior after > a fork (eg, a parent mmaps a file, madvises dontfork, then forks, and > the child writes to the page -- with madvise, the page is updated, > visible to both processes, as is the backing file, without it the child > will segfault) and thought there might be a simple typo. Typo: I flipped with and without madvise cases here. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
