[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0000000000006e8a3e05a41e5813@google.com>
Date: Sat, 25 Apr 2020 07:32:03 -0700
From: syzbot <syzbot+87a1b40b8fcdc9d40bd0@...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,
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 do_io_accounting (3)
syzbot suspects this bug was fixed by commit:
commit 76518d3798855242817e8a8ed76b2d72f4415624
Author: Bernd Edlinger <bernd.edlinger@...mail.de>
Date: Fri Mar 20 20:27:41 2020 +0000
proc: io_accounting: Use new infrastructure to fix deadlocks in execve
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=124347cfe00000
start commit: 46cf053e Linux 5.5-rc3
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ed9d672709340e35
dashboard link: https://syzkaller.appspot.com/bug?extid=87a1b40b8fcdc9d40bd0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15693866e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12847615e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: proc: io_accounting: 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