[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000001c5eaa05a357f2e1@google.com>
Date: Wed, 15 Apr 2020 10:50:02 -0700
From: syzbot <syzbot+d9ae59d4662c941e39c6@...kaller.appspotmail.com>
To: adobriyan@...il.com, akpm@...ux-foundation.org, avagin@...il.com,
bernd.edlinger@...mail.de, christian@...uner.io,
ebiederm@...ssion.com, guro@...com, kent.overstreet@...il.com,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
mhocko@...e.com, syzkaller-bugs@...glegroups.com,
tglx@...utronix.de
Subject: Re: possible deadlock in proc_pid_personality
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=136aea00100000
start commit: 63623fd4 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=5d2e033af114153f
dashboard link: https://syzkaller.appspot.com/bug?extid=d9ae59d4662c941e39c6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1374670de00000
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