From 4d317ded24c674d9ce64ff411ba292b955353b75 Mon Sep 17 00:00:00 2001 From: alc Date: Tue, 3 Nov 2009 17:15:15 +0000 Subject: 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 --- sys/vm/vm_fault.c | 11 ----------- 1 file changed, 11 deletions(-) (limited to 'sys/vm/vm_fault.c') diff --git a/sys/vm/vm_fault.c b/sys/vm/vm_fault.c index de87183..55b4173 100644 --- a/sys/vm/vm_fault.c +++ b/sys/vm/vm_fault.c @@ -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; -- cgit v1.1