From: syzbot <syzbot+217d60b447573313b211@syzkaller.appspotmail.com>
To: jencce.kernel@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, mszeredi@redhat.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in pipe_lock (3)
Date: Sun, 15 Mar 2020 09:19:03 -0700 [thread overview]
Message-ID: <0000000000009c33d905a0e70f63@google.com> (raw)
In-Reply-To: <000000000000fb27f1059aa202ea@google.com>
syzbot suspects this bug was fixed by commit:
commit 1a980b8cbf0059a5308eea61522f232fd03002e2
Author: Murphy Zhou <jencce.kernel@gmail.com>
Date: Fri Jan 17 12:49:29 2020 +0000
ovl: add splice file read write helper
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12dd7dc3e00000
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=217d60b447573313b211
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116496c1e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10104649e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: ovl: add splice file read write helper
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-03-15 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 21:25 possible deadlock in pipe_lock (3) syzbot
2020-03-15 16:19 ` 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=0000000000009c33d905a0e70f63@google.com \
--to=syzbot+217d60b447573313b211@syzkaller.appspotmail.com \
--cc=jencce.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--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).