From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: syzbot <syzbot+e4c8abb920efa77bace9@syzkaller.appspotmail.com>
Cc: alsa-devel-bounces@alsa-project.org, alsa-devel@alsa-project.org,
colin.king@canonical.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, perex@perex.cz, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, tiwai@suse.com
Subject: Re: WARNING in port_delete
Date: Mon, 1 Apr 2019 12:24:14 -0700 [thread overview]
Message-ID: <20190401192413.GQ4102@linux.ibm.com> (raw)
In-Reply-To: <0000000000002402ed05857361e0@google.com>
On Mon, Apr 01, 2019 at 12:58:01AM -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 63d86a7e85f84b8ac3b2f394570965aedbb03787
> Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Date: Tue May 1 20:08:46 2018 +0000
>
> rcu: Convert rcu_grace_period_init tracepoint to gp_seq
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17f86d2f200000
> start commit: 091a1eaa Merge branch 'akpm'
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=14046d2f200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10046d2f200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb
> dashboard link: https://syzkaller.appspot.com/bug?extid=e4c8abb920efa77bace9
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=102e2c91400000
>
> Reported-by: syzbot+e4c8abb920efa77bace9@syzkaller.appspotmail.com
> Fixes: 63d86a7e85f8 ("rcu: Convert rcu_grace_period_init tracepoint
> to gp_seq")
I could easily be suffering from a lack of imagination, but I am not
seeing how this change to RCU's event tracing could cause this result.
Especially given that CONFIG_RCU_TRACE=n in your .config.
What am I missing here?
Thanx, Paul
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
next prev parent reply other threads:[~2019-04-01 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 19:55 WARNING in port_delete syzbot
2018-10-06 12:58 ` syzbot
2019-04-01 7:58 ` syzbot
2019-04-01 19:24 ` Paul E. McKenney [this message]
2019-04-02 13:12 ` Dmitry Vyukov
-- strict thread matches above, loose matches on Subject: below --
2018-07-24 3:36 Dae R. Jeong
2018-07-24 3:59 ` DaeRyong Jeong
2018-07-24 7:00 ` Takashi Iwai
2018-07-24 7:14 ` DaeRyong Jeong
2018-07-24 7:23 ` Takashi Iwai
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=20190401192413.GQ4102@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=alsa-devel-bounces@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=perex@perex.cz \
--cc=rostedt@goodmis.org \
--cc=syzbot+e4c8abb920efa77bace9@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.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).