* Liam R. Howlett [220516 13:59]: > * Andrew Morton [220514 16:50]: > > On Sat, 14 May 2022 13:18:26 -0700 syzbot wrote: > > > > > syzbot has found a reproducer for the following issue on: > > > > > > HEAD commit: 1e1b28b936ae Add linux-next specific files for 20220513 > > > git tree: linux-next > > > console+strace: https://syzkaller.appspot.com/x/log.txt?x=11da21b9f00000 > > > kernel config: https://syzkaller.appspot.com/x/.config?x=e4eb3c0c4b289571 > > > dashboard link: https://syzkaller.appspot.com/bug?extid=ee1fdd8dcc770a3a169a > > > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142757f1f00000 > > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17cf0966f00000 > > > > Thanks. > > > > So it was there on April 28 and it's there now. Liam, do you think > > anything in the mapletree changes could have perturbed the interval > > tree handling? > > It is certainly possible, these two trees are intertwined so much. One > area that sticks out as a possibility is vma_expand(). I created a > vma_expand() function to handle growing a vma and potentially removing > the next vma. I do some interval tree modifications in there. > > I'll add it to my list of items to look at. This was my bug. I reused a pointer that wasn't reused in this function until I altered the error path in this commit. Please apply this patch to the maple tree series to fix "mm/mmap: use advanced maple tree API for mmap_region()" Thanks, Liam