From: syzbot <syzbot+a55ccfc8a853d3cff213@syzkaller.appspotmail.com>
To: amir73il@gmail.com, ast@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in path_openat
Date: Sun, 17 Nov 2019 18:14:01 -0800 [thread overview]
Message-ID: <00000000000042f41905979580cc@google.com> (raw)
In-Reply-To: <00000000000044cbf80576baaecd@google.com>
syzbot has bisected this bug to:
commit 8e54cadab447dae779f80f79c87cbeaea9594f60
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Sun Nov 27 01:05:42 2016 +0000
fix default_file_splice_read()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=108f4416e00000
start commit: 6d906f99 Merge tag 'arm64-fixes' of git://git.kernel.org/p..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=128f4416e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=148f4416e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=856fc6d0fbbeede9
dashboard link: https://syzkaller.appspot.com/bug?extid=a55ccfc8a853d3cff213
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101767b7200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13c15013200000
Reported-by: syzbot+a55ccfc8a853d3cff213@syzkaller.appspotmail.com
Fixes: 8e54cadab447 ("fix default_file_splice_read()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-18 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 23:44 possible deadlock in path_openat syzbot
2018-09-26 4:33 ` Miklos Szeredi
2018-09-27 6:05 ` Amir Goldstein
2018-09-27 6:36 ` Miklos Szeredi
2018-09-27 8:26 ` Amir Goldstein
2019-04-19 5:25 ` syzbot
2019-04-19 5:31 ` syzbot
2019-11-18 2:14 ` 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=00000000000042f41905979580cc@google.com \
--to=syzbot+a55ccfc8a853d3cff213@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=ast@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=syzkaller-bugs@googlegroups.com \
--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).