Do not coalesce if the swap object belongs to tmpfs vnode. The
coalesce would extend the object to keep pages for the anonymous mapping created by the process. The pages has no relations to the tmpfs file content which could be written into the corresponding range, causing anonymous mapping and file content aliasing and subsequent corruption. Another lesser problem created by coalescing is over-accounting on the tmpfs node destruction, since the object size is substracted from the total count of the pages owned by the tmpfs mount. Reported and tested by: bdrewery Sponsored by: The FreeBSD Foundation MFC after: 1 week
This commit is contained in:
parent
2547e15155
commit
79db892faa
@ -2099,8 +2099,9 @@ vm_object_coalesce(vm_object_t prev_object, vm_ooffset_t prev_offset,
|
||||
if (prev_object == NULL)
|
||||
return (TRUE);
|
||||
VM_OBJECT_WLOCK(prev_object);
|
||||
if (prev_object->type != OBJT_DEFAULT &&
|
||||
prev_object->type != OBJT_SWAP) {
|
||||
if ((prev_object->type != OBJT_DEFAULT &&
|
||||
prev_object->type != OBJT_SWAP) ||
|
||||
(prev_object->flags & OBJ_TMPFS) != 0) {
|
||||
VM_OBJECT_WUNLOCK(prev_object);
|
||||
return (FALSE);
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user