From: syzbot <syzbot+4c50ac32e5b10e4133e1@syzkaller.appspotmail.com>
To: andriin@fb.com, ast@kernel.org, axboe@kernel.dk,
bkkarthik@pesu.pes.edu, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, ebiggers@kernel.org,
hch@infradead.org, john.fastabend@gmail.com, kafai@fb.com,
kpsingh@chromium.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mcgrof@kernel.org, netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
yhs@fb.com
Subject: Re: WARNING in submit_bio_checks
Date: Wed, 15 Jul 2020 22:00:05 -0700 [thread overview]
Message-ID: <000000000000ef406d05aa87e9ba@google.com> (raw)
In-Reply-To: <00000000000029663005aa23cff4@google.com>
syzbot has bisected this issue to:
commit 449325b52b7a6208f65ed67d3484fd7b7184477b
Author: Alexei Starovoitov <ast@kernel.org>
Date: Tue May 22 02:22:29 2018 +0000
umh: introduce fork_usermode_blob() helper
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10fc4b00900000
start commit: 9e50b94b Add linux-next specific files for 20200703
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12fc4b00900000
console output: https://syzkaller.appspot.com/x/log.txt?x=14fc4b00900000
kernel config: https://syzkaller.appspot.com/x/.config?x=f99cc0faa1476ed6
dashboard link: https://syzkaller.appspot.com/bug?extid=4c50ac32e5b10e4133e1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1111fb6d100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1218fa1f100000
Reported-by: syzbot+4c50ac32e5b10e4133e1@syzkaller.appspotmail.com
Fixes: 449325b52b7a ("umh: introduce fork_usermode_blob() helper")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2020-07-16 5:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <00000000000029663005aa23cff4@google.com>]
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=000000000000ef406d05aa87e9ba@google.com \
--to=syzbot+4c50ac32e5b10e4133e1@syzkaller.appspotmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bkkarthik@pesu.pes.edu \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yhs@fb.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 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).