From: Dmitry Vyukov <dvyukov@google.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: syzbot <syzbot+7d03c810e50aaedef98a@syzkaller.appspotmail.com>,
dzickus@redhat.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
npiggin@gmail.com, Philippe Ombredanne <pombredanne@nexb.com>,
syzkaller-bugs@googlegroups.com,
Thomas Gleixner <tglx@linutronix.de>,
"the arch/x86 maintainers" <x86@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: INFO: rcu detected stall in xfrm_confirm_neigh
Date: Mon, 19 Feb 2018 11:05:38 +0100 [thread overview]
Message-ID: <CACT4Y+ZNFC0sBUd+ikf64N6vv26v-GcqD+M2p7q=gDDw-LkBQQ@mail.gmail.com> (raw)
In-Reply-To: <20180219072243.vk7ow4gdpqhz5gbp@gauss3.secunet.de>
On Mon, Feb 19, 2018 at 8:22 AM, Steffen Klassert
<steffen.klassert@secunet.com> wrote:
>> > <syzbot+7d03c810e50aaedef98a@syzkaller.appspotmail.com> wrote:
>> >> Hello,
>> >>
>> >> syzbot hit the following crash on net-next commit
>> >> 9515a2e082f91457db0ecff4b65371d0fb5d9aad (Thu Jan 25 03:37:38 2018 +0000)
>> >> net/ipv4: Allow send to local broadcast from a socket bound to a VRF
>> >>
>> >> So far this crash happened 6 times on net-next.
>> >> Unfortunately, I don't have any reproducer for this crash yet.
>> >> Raw console output is attached.
>> >> compiler: gcc (GCC) 7.1.1 20170620
>> >> .config is attached.
>> >
>> >
>> > +xfrm maintainers
>>
>> Here is a C repro:
>> https://gist.githubusercontent.com/dvyukov/92c67ba9afaaa960bcfbdc6ef549ac10/raw/786f9221c1d707c7f4a15effcb1d5997dd4f8638/gistfile1.txt
>
> Seems like syzbot does not know about this reproducer.
>
> I've send a patch to test and got this as the reply:
>
> This crash does not have a reproducer. I cannot test it.
Yes, it does not know about the reproducer. I've extracted it
manually, these hangs are sometimes hard to reproduce. For syzbot this
bug does not have a reproducer.
Have you tried to run the reproducer? For me it reproduced the bug
quite reliably.
next prev parent reply other threads:[~2018-02-19 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1141ba9ea381f70565057687@google.com>
2018-02-12 15:26 ` INFO: rcu detected stall in xfrm_confirm_neigh Dmitry Vyukov
2018-02-13 9:19 ` Dmitry Vyukov
2018-02-19 7:22 ` Steffen Klassert
2018-02-19 10:05 ` Dmitry Vyukov [this message]
2018-02-20 9:53 ` Steffen Klassert
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='CACT4Y+ZNFC0sBUd+ikf64N6vv26v-GcqD+M2p7q=gDDw-LkBQQ@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=davem@davemloft.net \
--cc=dzickus@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pombredanne@nexb.com \
--cc=steffen.klassert@secunet.com \
--cc=syzbot+7d03c810e50aaedef98a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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).