Re: [PATCH 0/3] mm: Fix misuse of parent anon_vma in dup_mmap path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat,  8 Feb 2020 08:35:25 +0000 Li Xinhai <lixinhai.lxh@xxxxxxxxx> wrote:

> This patchset fix the misuse of parenet anon_vma, which mainly caused by
> child vma's vm_next and vm_prev are left same as its parent after
> duplicate vma. Finally, code reached parent vma's neighbor by referring
> pointer of child vma and executed wrong logic.
> 
> The first two patches fix relevant issues, and the third patch sets vm_next
> and vm_prev to NULL when duplicate vma to prevent potential misuse in future. 
> 
> Li Xinhai (3):
>   mm: don't prepare anon_vma if vma has VM_WIPEONFORK
>   Revert "mm/rmap.c: reuse mergeable anon_vma as parent when fork"
>   mm: set vm_next and vm_prev to NULL in vm_area_dup()
> 
>  kernel/fork.c | 10 ++++++----
>  mm/rmap.c     | 13 -------------
>  2 files changed, 6 insertions(+), 17 deletions(-)

Can we please have some review input on this series?




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux