From: Borislav Petkov <bp@alien8.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
konrad.wilk@oracle.com, Len Brown <len.brown@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
puwen@hygon.cn, syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Thomas Gleixner <tglx@linutronix.de>,
wang.yi59@zte.com.cn, the arch/x86 maintainers <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: WARNING in rcu_check_gp_start_stall
Date: Sat, 23 Feb 2019 11:56:48 +0100 [thread overview]
Message-ID: <20190223105638.GA27239@zn.tnic> (raw)
In-Reply-To: <CACT4Y+ZaUe+_ZT4tLpXWUtfih4ocNgAsa4WdV4NRceLdK4tc4Q@mail.gmail.com>
On Sat, Feb 23, 2019 at 11:50:49AM +0100, Dmitry Vyukov wrote:
> Peter, what is the canonical location to reference for this issue
> (open bug or something)? When we get back to this report later, how
> does one know if this is fixed or not and what's the status?
bugzilla.kernel.org maybe?
> The C repro hanged the machine even faster, so it must be some other difference.
> I would expect compiler to not make difference. qemu, number of CPUs
> and maybe host kernel config (at least for interrupt granularity or
> something?) may be relevant.
>
> But if you want to run syzkaller reproducer with syz-execprog, there
> is a docs link in the "syz repro" link.
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-02-23 10:57 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
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 [this message]
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=20190223105638.GA27239@zn.tnic \
--to=bp@alien8.de \
--cc=dvyukov@google.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=peterz@infradead.org \
--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 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).