Eliminate a bit of hackery from vm_fault(). The operations that this
hackery sought to prevent are now properly supported by vm_map_protect(). (See r198505.) Reviewed by: kib
This commit is contained in:
parent
1b9d701fee
commit
86684848b6
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=198855
@ -264,17 +264,6 @@ RetryFault:;
|
||||
&fs.entry, &fs.first_object, &fs.first_pindex, &prot, &wired);
|
||||
if (result != KERN_SUCCESS)
|
||||
return (result);
|
||||
|
||||
/*
|
||||
* If we don't COW now, on a user wire, the user will never
|
||||
* be able to write to the mapping. If we don't make this
|
||||
* restriction, the bookkeeping would be nearly impossible.
|
||||
*
|
||||
* XXX The following assignment modifies the map without
|
||||
* holding a write lock on it.
|
||||
*/
|
||||
if ((fs.entry->protection & VM_PROT_WRITE) == 0)
|
||||
fs.entry->max_protection &= ~VM_PROT_WRITE;
|
||||
}
|
||||
|
||||
map_generation = fs.map->timestamp;
|
||||
|
Loading…
Reference in New Issue
Block a user