From: Arjan van de Ven <arjan@linux.intel.com>
To: paulmck@linux.ibm.com, Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+43f6755d1c2e62743468@syzkaller.appspotmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Josh Triplett <josh@joshtriplett.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: WARNING in __rcu_read_unlock
Date: Mon, 17 Dec 2018 06:14:13 -0800 [thread overview]
Message-ID: <1583d5fc-34bf-3a81-363d-01a1085a7363@linux.intel.com> (raw)
In-Reply-To: <20181217112916.GG4170@linux.ibm.com>
On 12/17/2018 3:29 AM, Paul E. McKenney wrote:
> As does this sort of report on a line that contains simple integer
> arithmetic and boolean operations.;-)
>
> Any chance of a bisection?
btw this looks like something caused a stack overflow and thus all the weirdness that then happens
next prev parent reply other threads:[~2018-12-17 14:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 12:41 syzbot
2018-12-16 19:04 ` Paul E. McKenney
2018-12-17 9:44 ` Dmitry Vyukov
2018-12-17 11:29 ` Paul E. McKenney
2018-12-17 13:07 ` Dmitry Vyukov
2018-12-17 14:14 ` Arjan van de Ven [this message]
2018-12-17 14:40 ` Dmitry Vyukov
2018-12-17 14:49 ` Paul E. McKenney
2018-12-17 14:57 ` Eric Dumazet
2018-12-17 14:59 ` Stefano Brivio
2018-12-17 15:11 ` Dmitry Vyukov
2018-12-17 15:24 ` Stefano Brivio
2018-12-17 15:53 ` Dmitry Vyukov
2018-12-17 23:18 ` Stefano Brivio
2018-12-18 8:49 ` Dmitry Vyukov
2018-12-18 12:40 ` Stefano Brivio
2018-12-18 13:26 ` Dmitry Vyukov
2018-12-18 14:02 ` Paul E. McKenney
2018-12-18 14:12 ` Stefano Brivio
2018-12-18 16:05 ` Dmitry Vyukov
2018-12-19 4:12 ` Cong Wang
2018-12-17 18:21 ` Stefano Brivio
2018-12-17 18:45 ` Dmitry Vyukov
2018-12-17 19:56 ` Paul E. McKenney
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=1583d5fc-34bf-3a81-363d-01a1085a7363@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=syzbot+43f6755d1c2e62743468@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
Powered by JetHome