Re: [PATCH] fix VmSize and VmData after mremap

2005-08-05 Thread Frank van Maarseveen
On Thu, Aug 04, 2005 at 07:05:30PM +0100, Hugh Dickins wrote: > mremap's move_vma is applying __vm_stat_account to the old vma which may > have already been freed: move it to just before the do_munmap. > > mremapping to and fro with CONFIG_DEBUG_SLAB=y showed /proc//status > VmSize and VmData

Re: [PATCH] fix VmSize and VmData after mremap

2005-08-05 Thread Frank van Maarseveen
On Thu, Aug 04, 2005 at 07:05:30PM +0100, Hugh Dickins wrote: mremap's move_vma is applying __vm_stat_account to the old vma which may have already been freed: move it to just before the do_munmap. mremapping to and fro with CONFIG_DEBUG_SLAB=y showed /proc/pid/status VmSize and VmData

[PATCH] fix VmSize and VmData after mremap

2005-08-04 Thread Hugh Dickins
mremap's move_vma is applying __vm_stat_account to the old vma which may have already been freed: move it to just before the do_munmap. mremapping to and fro with CONFIG_DEBUG_SLAB=y showed /proc//status VmSize and VmData wrapping just like in kernel bugzilla #4842, and fixed by this patch -

[PATCH] fix VmSize and VmData after mremap

2005-08-04 Thread Hugh Dickins
mremap's move_vma is applying __vm_stat_account to the old vma which may have already been freed: move it to just before the do_munmap. mremapping to and fro with CONFIG_DEBUG_SLAB=y showed /proc/pid/status VmSize and VmData wrapping just like in kernel bugzilla #4842, and fixed by this patch -