[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0000000000009e3eb505a4a7759e@google.com>
Date: Sat, 02 May 2020 03:07:03 -0700
From: syzbot <syzbot+985c8a3c7f3668d31a49@...kaller.appspotmail.com>
To: adobriyan@...il.com, akpm@...ux-foundation.org, avagin@...il.com,
bernd.edlinger@...mail.de, casey@...aufler-ca.com,
christian@...uner.io, ebiederm@...ssion.com, guro@...com,
kent.overstreet@...il.com, khlebnikov@...dex-team.ru,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
mhocko@...e.com, shakeelb@...gle.com,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de
Subject: Re: possible deadlock in lock_trace (3)
syzbot suspects this bug was fixed by commit:
commit 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696
Author: Bernd Edlinger <bernd.edlinger@...mail.de>
Date: Fri Mar 20 20:27:24 2020 +0000
proc: Use new infrastructure to fix deadlocks in execve
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17222ec4100000
start commit: a42a7bb6 Merge tag 'irq-urgent-2020-03-15' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c2e311dba9a02ba9
dashboard link: https://syzkaller.appspot.com/bug?extid=985c8a3c7f3668d31a49
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1185f753e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: proc: Use new infrastructure to fix deadlocks in execve
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Powered by blists - more mailing lists