This patch is a meager attempt to correct that.
Details
- Reviewers
kib markj - Group Reviewers
manpages - Commits
- rS349379: Document the KERN_PROTECTION_FAILURE return value from vm_map_protect().
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
vm_map_protect.9 | ||
---|---|---|
99 | The range isn't being allocated. It is copy-on-write, and it is transitioning from read-only to read/write. |
vm_map_protect.9 | ||
---|---|---|
100 | I think it is somewhat too cryptic. 'If copy-on-write mapping is transitioned from ro to rw, too little swap space is available for backing the copied pages'. |
vm_map_protect.9 | ||
---|---|---|
99 | "If a copy-on-write mapping is transitioned from read-only to read-write..." |
vm_map_protect.9 | ||
---|---|---|
99 | Still missing an article: "If a copy-on-write..." |
If mips32 + SMP ends up not being a thing anymore due to the recent 64-bit atomic debate, this function can just be removed.
Otherwise, is there a good way for me to exercise that config? I'm open to buying real HW...