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. What are the runtime effects of this bug? How is the bug triggered?
