This patch introduces a new bug. While it does guarantee that the assertion in vm_object_shadow isn't tripped over, it doesn't clear the OBJ_ONEMAPPING flag on the newly created shadow object. (New objects are created with OBJ_ONEMAPPING set.) Consequently, we'll have two overlapping mappings to the same shadow object that has OBJ_ONEMAPPING set. That's bad. The real problem is that the assertion is just plain wrong, not the code around it. It needs to be corrected or removed. Alan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: panic: vm_object_shado... Matthew Dillon
- Re: panic: vm_object_shado... Alan Cox
- Re: panic: vm_object_shado... Matthew Dillon
- Re: panic: vm_object_shadow: source... Brian Fundakowski Feldman
- Re: panic: vm_object_shadow: so... Alan Cox
- Re: panic: vm_object_shadow: source object ... Brian Fundakowski Feldman
- Re: panic: vm_object_shadow: source obj... Matthew Dillon
- Re: panic: vm_object_shadow: source... Brian Fundakowski Feldman
- Anyone able to verify the fix f... Matthew Dillon
- Re: Anyone able to verify ... Michael Reifenberger
- Re: Anyone able to verify ... Alan Cox
- Re: Anyone able to verify ... Matthew Dillon
- Re: Anyone able to verify ... Brian Fundakowski Feldman
- Re: Anyone able to verify ... Alan Cox
- Re: Anyone able to verify ... Matthew Dillon
- Re: panic: vm_object_shadow: source object has O... Matthew Dillon
- Re: panic: vm_object_shadow: source object ... Alfred Perlstein
- Re: panic: vm_object_shadow: source obj... Matthew Dillon