From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f42.google.com ([209.85.160.42]:44877 "EHLO mail-pl0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752249AbeBSKGA (ORCPT ); Mon, 19 Feb 2018 05:06:00 -0500 Received: by mail-pl0-f42.google.com with SMTP id w21so5365334plp.11 for ; Mon, 19 Feb 2018 02:06:00 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20180219072243.vk7ow4gdpqhz5gbp@gauss3.secunet.de> References: <001a1141ba9ea381f70565057687@google.com> <20180219072243.vk7ow4gdpqhz5gbp@gauss3.secunet.de> From: Dmitry Vyukov Date: Mon, 19 Feb 2018 11:05:38 +0100 Message-ID: Subject: Re: INFO: rcu detected stall in xfrm_confirm_neigh To: Steffen Klassert Cc: syzbot , dzickus@redhat.com, Greg Kroah-Hartman , "H. Peter Anvin" , Kate Stewart , LKML , Ingo Molnar , npiggin@gmail.com, Philippe Ombredanne , syzkaller-bugs@googlegroups.com, Thomas Gleixner , "the arch/x86 maintainers" , Herbert Xu , David Miller , netdev Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Feb 19, 2018 at 8:22 AM, Steffen Klassert wrote: >> > 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.