From: syzbot <syzbot+87a1b40b8fcdc9d40bd0@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org, avagin@gmail.com,
bernd.edlinger@hotmail.de, casey@schaufler-ca.com,
christian@brauner.io, ebiederm@xmission.com,
kent.overstreet@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mhocko@suse.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: possible deadlock in do_io_accounting (3)
Date: Sat, 25 Apr 2020 07:32:03 -0700 [thread overview]
Message-ID: <0000000000006e8a3e05a41e5813@google.com> (raw)
In-Reply-To: <0000000000006233e4059aa1dfb6@google.com>
syzbot suspects this bug was fixed by commit:
commit 76518d3798855242817e8a8ed76b2d72f4415624
Author: Bernd Edlinger <bernd.edlinger@hotmail.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
prev parent reply other threads:[~2020-04-25 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 21:15 possible deadlock in do_io_accounting (3) syzbot
2019-12-27 3:04 ` syzbot
2019-12-27 11:55 ` syzbot
2020-04-25 14:32 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000006e8a3e05a41e5813@google.com \
--to=syzbot+87a1b40b8fcdc9d40bd0@syzkaller.appspotmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=bernd.edlinger@hotmail.de \
--cc=casey@schaufler-ca.com \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.