From: syzbot <syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com>
To: amir73il@gmail.com, ast@kernel.org, dvyukov@google.com,
linux-fsdevel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
mszeredi@redhat.com, rgoldwyn@suse.de,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
zohar@linux.ibm.com, zohar@linux.vnet.ibm.com
Subject: Re: possible deadlock in mnt_want_write
Date: Fri, 22 Nov 2019 18:27:00 -0800 [thread overview]
Message-ID: <000000000000ebac4d0597fa4340@google.com> (raw)
In-Reply-To: <000000000000d03eea0571adfe83@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=15147a36e00000
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=17147a36e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=13147a36e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=856fc6d0fbbeede9
dashboard link: https://syzkaller.appspot.com/bug?extid=ae82084b07d0297e566b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111767b7200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1611ab2d200000
Reported-by: syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com
Fixes: 8e54cadab447 ("fix default_file_splice_read()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-23 2:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 17:30 possible deadlock in mnt_want_write syzbot
2018-11-21 16:14 ` syzbot
2018-11-21 16:24 ` syzbot
2018-11-21 18:57 ` Amir Goldstein
2018-11-21 20:04 ` Goldwyn Rodrigues
2018-11-21 20:22 ` Amir Goldstein
2019-11-23 2:27 ` syzbot [this message]
2020-11-07 12:10 ` syzbot
2020-11-11 13:52 ` Dmitry Vyukov
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=000000000000ebac4d0597fa4340@google.com \
--to=syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=ast@kernel.org \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=rgoldwyn@suse.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.ibm.com \
--cc=zohar@linux.vnet.ibm.com \
/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.