From: syzbot <syzbot+98704a51af8e3d9425a9@syzkaller.appspotmail.com>
To: idryomov@gmail.com, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
xiubli@redhat.com
Subject: Re: BUG: sleeping function called from invalid context in __kmalloc
Date: Fri, 07 Feb 2020 13:58:01 -0800 [thread overview]
Message-ID: <000000000000be1109059e037b83@google.com> (raw)
In-Reply-To: <000000000000d895bd059dffb65c@google.com>
syzbot has bisected this bug to:
commit 4fbc0c711b2464ee1551850b85002faae0b775d5
Author: Xiubo Li <xiubli@redhat.com>
Date: Fri Dec 20 14:34:04 2019 +0000
ceph: remove the extra slashes in the server path
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=166a57bee00000
start commit: 90568ecf Merge tag 'kvm-5.6-2' of git://git.kernel.org/pub..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=156a57bee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=116a57bee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=69fa012479f9a62
dashboard link: https://syzkaller.appspot.com/bug?extid=98704a51af8e3d9425a9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=172182b5e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1590aab5e00000
Reported-by: syzbot+98704a51af8e3d9425a9@syzkaller.appspotmail.com
Fixes: 4fbc0c711b24 ("ceph: remove the extra slashes in the server path")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-02-07 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 17:28 BUG: sleeping function called from invalid context in __kmalloc syzbot
2020-02-07 17:44 ` syzbot
2020-02-07 18:44 ` Al Viro
2020-02-07 18:52 ` Jeff Layton
2020-02-07 21:58 ` 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=000000000000be1109059e037b83@google.com \
--to=syzbot+98704a51af8e3d9425a9@syzkaller.appspotmail.com \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xiubli@redhat.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).