[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250717023444.2281-1-hdanton@sina.com>
Date: Thu, 17 Jul 2025 10:34:43 +0800
From: Hillf Danton <hdanton@...a.com>
To: syzbot <syzbot+159a3ef1894076a6a6e9@...kaller.appspotmail.com>
Cc: linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com,
lorenzo.stoakes@...cle.com,
surenb@...gle.com,
linux-mm@...ck.org
Subject: Re: [syzbot] [mm?] possible deadlock in lock_next_vma
> Date: Mon, 14 Jul 2025 09:38:33 -0700 [thread overview]
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 0be23810e32e Add linux-next specific files for 20250714
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15cfb0f0580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=be9e2082003f81ff
> dashboard link: https://syzkaller.appspot.com/bug?extid=159a3ef1894076a6a6e9
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1003b18c580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11437d82580000
Test [PATCH v7 0/7] use per-vma locks for /proc/pid/maps reads
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
Powered by blists - more mailing lists