From: syzbot <syzbot+2a73a6ea9507b7112141@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, gregkh@linuxfoundation.org,
kstewart@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
mszeredi@redhat.com, oleg@redhat.com, paulmck@linux.vnet.ibm.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in acct_pin_kill
Date: Tue, 26 Mar 2019 20:53:01 -0700 [thread overview]
Message-ID: <000000000000c51f7505850b5f3e@google.com> (raw)
In-Reply-To: <0000000000007dedf00576dd53eb@google.com>
syzbot has bisected this bug to:
commit e950564b97fd0f541b02eb207685d0746f5ecf29
Author: Miklos Szeredi <mszeredi@redhat.com>
Date: Tue Jul 24 13:01:55 2018 +0000
vfs: don't evict uninitialized inode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12123143200000
start commit: da5322e6 Merge tag 'selinux-pr-20181115' of git://git.kern..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=11123143200000
console output: https://syzkaller.appspot.com/x/log.txt?x=16123143200000
kernel config: https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
dashboard link: https://syzkaller.appspot.com/bug?extid=2a73a6ea9507b7112141
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12298533400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ff545d400000
Reported-by: syzbot+2a73a6ea9507b7112141@syzkaller.appspotmail.com
Fixes: e950564b97fd ("vfs: don't evict uninitialized inode")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2019-03-27 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000007dedf00576dd53eb@google.com>
2019-03-27 3:53 ` syzbot [this message]
2019-03-27 7:16 ` possible deadlock in acct_pin_kill Amir Goldstein
2019-03-27 15:18 ` syzbot
2019-03-28 8:23 ` Dmitry Vyukov
2019-04-19 7:52 ` Amir Goldstein
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=000000000000c51f7505850b5f3e@google.com \
--to=syzbot+2a73a6ea9507b7112141@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mszeredi@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).