From: Borislav Petkov <bp@alien8.de>
To: syzbot <syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com>
Cc: douly.fnst@cn.fujitsu.com, hpa@zytor.com, konrad.wilk@oracle.com,
len.brown@intel.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, puwen@hygon.cn,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
wang.yi59@zte.com.cn, x86@kernel.org
Subject: Re: WARNING in rcu_check_gp_start_stall
Date: Fri, 22 Feb 2019 23:20:36 +0100 [thread overview]
Message-ID: <20190222222036.GC30766@zn.tnic> (raw)
In-Reply-To: <0000000000007da94e05827ea99a@google.com>
On Fri, Feb 22, 2019 at 09:10:04AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 8a61716ff2ab Merge tag 'ceph-for-5.0-rc8' of git://github...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1531dd3f400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f
> dashboard link: https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d4966cc00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c492d0c00000
So I ran this for more than an hour in a guest here with the above
.config but nothing happened. The compiler I used is 8.2, dunno of that
makes the difference or I'm missing something else...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-02-22 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 17:10 WARNING in rcu_check_gp_start_stall syzbot
2019-02-22 22:20 ` Borislav Petkov [this message]
2019-02-23 10:33 ` Dmitry Vyukov
2019-02-23 10:38 ` Borislav Petkov
2019-02-23 10:50 ` Dmitry Vyukov
2019-02-23 10:56 ` Borislav Petkov
2019-03-17 10:43 ` syzbot
2019-03-17 11:04 ` Greg KH
2019-03-18 12:18 ` Dmitry Vyukov
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=20190222222036.GC30766@zn.tnic \
--to=bp@alien8.de \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=puwen@hygon.cn \
--cc=syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=wang.yi59@zte.com.cn \
--cc=x86@kernel.org \
/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.