From: syzbot <syzbot+d9ae59d4662c941e39c6@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org, avagin@gmail.com,
bernd.edlinger@hotmail.de, christian@brauner.io,
ebiederm@xmission.com, guro@fb.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 proc_pid_personality
Date: Wed, 15 Apr 2020 10:50:02 -0700 [thread overview]
Message-ID: <0000000000001c5eaa05a357f2e1@google.com> (raw)
In-Reply-To: <000000000000f8a16405a0376780@google.com>
syzbot suspects this bug was fixed by commit:
commit 2db9dbf71bf98d02a0bf33e798e5bfd2a9944696
Author: Bernd Edlinger <bernd.edlinger@hotmail.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
next prev parent reply other threads:[~2020-04-15 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 22:45 possible deadlock in proc_pid_personality syzbot
2020-04-15 17:50 ` syzbot [this message]
2020-04-15 18:28 ` [PATCH] proc: Handle umounts cleanly Eric W. Biederman
2020-04-15 19:36 ` Christian Brauner
2020-04-15 20:17 ` Eric W. Biederman
2020-04-15 21:20 ` Christian Brauner
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=0000000000001c5eaa05a357f2e1@google.com \
--to=syzbot+d9ae59d4662c941e39c6@syzkaller.appspotmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=bernd.edlinger@hotmail.de \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=guro@fb.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.