From: syzbot <syzbot+6fb8ff5211d3e821398f@syzkaller.appspotmail.com>
To: dvyukov@google.com, gregkh@linuxfoundation.org, hch@lst.de,
joey.jiaojg@gmail.com, linux-kernel@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp, sidgup@codeaurora.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] unexpected kernel reboot (5)
Date: Thu, 27 May 2021 05:12:09 -0700 [thread overview]
Message-ID: <00000000000025334e05c34eab2c@google.com> (raw)
In-Reply-To: <000000000000b808c705c345b35d@google.com>
syzbot has bisected this issue to:
commit f2d6c2708bd84ca953fa6b6ca5717e79eb0140c7
Author: Christoph Hellwig <hch@lst.de>
Date: Wed Jan 20 20:46:31 2021 +0000
kernfs: wire up ->splice_read and ->splice_write
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=144ee113d00000
start commit: 7ac3a1c1 Merge tag 'mtd/fixes-for-5.13-rc4' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=164ee113d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=124ee113d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=266cda122a0b56c
dashboard link: https://syzkaller.appspot.com/bug?extid=6fb8ff5211d3e821398f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154e8703d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=171382d3d00000
Reported-by: syzbot+6fb8ff5211d3e821398f@syzkaller.appspotmail.com
Fixes: f2d6c2708bd8 ("kernfs: wire up ->splice_read and ->splice_write")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-05-27 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 1:30 [syzbot] unexpected kernel reboot (5) syzbot
2021-05-27 2:08 ` syzbot
2021-05-27 6:40 ` Dmitry Vyukov
2021-05-27 6:59 ` Tetsuo Handa
[not found] ` <9B8B972A-EC9F-4806-9897-41581578646A@gmail.com>
2021-05-27 13:16 ` Tetsuo Handa
2021-05-31 8:50 ` Dmitry Vyukov
2021-05-27 12:12 ` 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=00000000000025334e05c34eab2c@google.com \
--to=syzbot+6fb8ff5211d3e821398f@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=joey.jiaojg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sidgup@codeaurora.org \
--cc=syzkaller-bugs@googlegroups.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.