@@ -647,7 +647,8 @@ compute_regions_to_munmap(RestoreInfo *rinfo)
647647
648648NO_OPTIMIZE
649649static void
650- restore_vdso_vvar_work (MemRegion * currentRegion , MemRegion * ckptRegion , const char * regionName )
650+ restore_vdso_vvar_work (MemRegion * currentRegion , MemRegion * ckptRegion ,
651+ const char * regionName )
651652{
652653 int mtcp_sys_errno ;
653654
@@ -677,7 +678,8 @@ restore_vdso_vvar(RestoreInfo *rinfo)
677678{
678679 restore_vdso_vvar_work (& rinfo -> currentVdso , & rinfo -> ckptHdr .vdso , "[vdso]" );
679680 restore_vdso_vvar_work (& rinfo -> currentVvar , & rinfo -> ckptHdr .vvar , "[vvar]" );
680- restore_vdso_vvar_work (& rinfo -> currentVvarVClock , & rinfo -> ckptHdr .vvarVClock , "[vvar_vclock]" );
681+ restore_vdso_vvar_work (& rinfo -> currentVvarVClock , & rinfo -> ckptHdr .vvarVClock ,
682+ "[vvar_vclock]" );
681683
682684 if (rinfo -> currentVdso .startAddr != 0 ) {
683685 mtcp_setauxval (rinfo -> environ , AT_SYSINFO_EHDR ,
@@ -967,9 +969,9 @@ doAreasOverlap(Area *area, MemRegion *memRegion)
967969}
968970
969971/* This uses MREMAP_FIXED | MREMAP_MAYMOVE to move a memory segment.
970- * Note that we need 'MREMAP_MAYMOVE'. With only 'MREMAP_FIXED', the
971- * kernel can overwrite an existing memory region.
972- * Note that 'mremap' and hence 'mremap_move' do not allow overlapping src and dest.
972+ * Note that 'MREMAP_MAYMOVE' is required, if using 'MREMAP_FIXED'.
973+ * Note that 'mremap' and hence 'mremap_move' do not allow overlapping
974+ * src and dest.
973975 */
974976NO_OPTIMIZE
975977static int
@@ -987,7 +989,7 @@ mremap_move(void *dest, void *src, size_t size) {
987989 return -1 ; // Error
988990 } else {
989991 // Else 'MREMAP_MAYMOVE' forced the remap to the wrong location. So, the
990- // memory was moved to the wrong desgination . Undo the move, and return -1.
992+ // memory was moved to the wrong destination . Undo the move, and return -1.
991993 mremap_move (src , rc , size );
992994 return -1 ; // Error
993995 }
0 commit comments