From: syzbot <syzbot+e6f77e16ff68b2434a2c@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, ericvh@gmail.com, hch@infradead.org,
hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, lucho@ionkov.net, nazard@nazar.ca,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
v9fs-developer@lists.sourceforge.net, viro@zeniv.linux.org.uk
Subject: Re: WARNING in __kernel_write
Date: Tue, 14 Jul 2020 16:15:08 -0700 [thread overview]
Message-ID: <000000000000752cbc05aa6efa98@google.com> (raw)
In-Reply-To: <0000000000005f350105aa0af108@google.com>
syzbot has bisected this issue to:
commit 81238b2cff1469ff5b94390d026cd075105d6dcd
Author: Christoph Hellwig <hch@lst.de>
Date: Thu May 7 17:33:03 2020 +0000
fs: implement kernel_write using __kernel_write
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10d829bf100000
start commit: be978f8f Add linux-next specific files for 20200713
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12d829bf100000
console output: https://syzkaller.appspot.com/x/log.txt?x=14d829bf100000
kernel config: https://syzkaller.appspot.com/x/.config?x=3fe4fccb94cbc1a6
dashboard link: https://syzkaller.appspot.com/bug?extid=e6f77e16ff68b2434a2c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11fe004f100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d35f33100000
Reported-by: syzbot+e6f77e16ff68b2434a2c@syzkaller.appspotmail.com
Fixes: 81238b2cff14 ("fs: implement kernel_write using __kernel_write")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-07-14 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 23:54 WARNING in __kernel_write syzbot
2020-07-10 8:55 ` Christoph Hellwig
2020-07-14 23:15 ` 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=000000000000752cbc05aa6efa98@google.com \
--to=syzbot+e6f77e16ff68b2434a2c@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@gmail.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=nazard@nazar.ca \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs-developer@lists.sourceforge.net \
--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 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.