OpenBSD's kernel virtual/physical memory system, uvm(9), already had the ability to set permissions on mappings. But the recent work done here is still substant

OpenBSD's kernel virtual/physical memory system, uvm(9), already had the ability to set permissions on mappings. But the recent work done here is still substantial, API's were cleaned up and the W^X policy was applied in the places where memory was being mapped with both permissions (writable, executable). I'm not overly familiar with all that went into this, but reading the commit logs by both Theo and Mike might help clarify some of it. http://freshbsd.org/search?project=openbsd&q=file.name%3Aamd64&committer=mlarkin http://freshbsd.org/search?project=openbsd&q=file.name%3Aamd... http://freshbsd.org/search?project=openbsd&q=file.name%3Akern&committer=mlarkin http://freshbsd.org/search?project=openbsd&q=file.name%3Aker... http://freshbsd.org/search?project=openbsd&q=file.name%3Aamd64&committer=deraadt http://freshbsd.org/search?project=openbsd&q=file.name%3Aamd... http://freshbsd.org/search?project=openbsd&q=file.name%3Akern&committer=deraadt http://freshbsd.org/search?project=openbsd&q=file.name%3Aker...