From: Qian Cai <cai@lca.pw>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+7ef50afd3a211f879112@syzkaller.appspotmail.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
dev@openvswitch.org, kuba@kernel.org,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Pravin B Shelar <pshelar@ovn.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: linux-next test error: WARNING: suspicious RCU usage in ovs_ct_exit
Date: Sun, 19 Apr 2020 21:59:52 -0400 [thread overview]
Message-ID: <4A33114F-0173-4C12-8FD1-3F863318A4D3@lca.pw> (raw)
In-Reply-To: <CACT4Y+YR5Y8OQ4MCdCA2eoQM=GdBXN39O4HahWtL0sdqwsB=mg@mail.gmail.com>
> On Apr 18, 2020, at 3:02 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
>
> On Sat, Mar 14, 2020 at 8:57 AM syzbot
> <syzbot+7ef50afd3a211f879112@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit: 2e602db7 Add linux-next specific files for 20200313
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=16669919e00000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=cf2879fc1055b886
>> dashboard link: https://syzkaller.appspot.com/bug?extid=7ef50afd3a211f879112
>> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>>
>> Unfortunately, I don't have any reproducer for this crash yet.
>>
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+7ef50afd3a211f879112@syzkaller.appspotmail.com
>
> +linux-next, Stephen for currently open linux-next build/boot failure
>
>> =============================
>> WARNING: suspicious RCU usage
>> 5.6.0-rc5-next-20200313-syzkaller #0 Not tainted
>> -----------------------------
>> net/openvswitch/conntrack.c:1898 RCU-list traversed in non-reader section!
Those should be fixed by,
https://lore.kernel.org/netdev/1587063451-54027-1-git-send-email-xiangxia.m.yue@gmail.com/
>> =============================
>> WARNING: suspicious RCU usage
>> 5.6.0-rc5-next-20200313-syzkaller #0 Not tainted
>> -----------------------------
>> net/ipv4/ipmr.c:1757 RCU-list traversed in non-reader section!!
and,
https://lore.kernel.org/netdev/20200222063835.14328-1-frextrite@gmail.com/
It looks like both are waiting for David to pick up.
prev parent reply other threads:[~2020-04-20 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 7:57 linux-next test error: WARNING: suspicious RCU usage in ovs_ct_exit syzbot
2020-04-16 18:57 ` [PATCH] net: openvswitch: ovs_ct_exit to be done under ovs_lock xiangxia.m.yue
2020-04-19 17:32 ` Pravin Shelar
2020-04-20 18:00 ` David Miller
2020-04-18 7:02 ` linux-next test error: WARNING: suspicious RCU usage in ovs_ct_exit Dmitry Vyukov
2020-04-20 1:59 ` Qian Cai [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=4A33114F-0173-4C12-8FD1-3F863318A4D3@lca.pw \
--to=cai@lca.pw \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=dvyukov@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+7ef50afd3a211f879112@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 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.