From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E17A3C43613 for ; Mon, 24 Jun 2019 04:39:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AFFC92083D for ; Mon, 24 Jun 2019 04:39:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="GdD5hTA7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727853AbfFXEjN (ORCPT ); Mon, 24 Jun 2019 00:39:13 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:39724 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726343AbfFXEjM (ORCPT ); Mon, 24 Jun 2019 00:39:12 -0400 Received: by mail-wm1-f68.google.com with SMTP id z23so11829855wma.4; Sun, 23 Jun 2019 21:39:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YNELeqsO3ONkBzigACa9WgfAHnyRLEL6gV/TACazJzc=; b=GdD5hTA7BPb+tN5+F5Hd9Yjg3qpZhl/UDMGlGoEM7GFhcuPKCjk0fDtp6trqGu4LaZ lvZ6ASMBEqBCwbDlZLWIct7GQlpvDPbQscSsh0OGcsO4nqEikUUVnb7hxe5h5ecAQ/+x y5TX9lYlEQ0vRsrCzItt5ktQhH1F7Ffl0oWXTHP3u6/1e6hJZt3fg4VsTKqFGQru2cbt uKaRHBxTbjBYrVvT22A/wpLycOGrxVzAPdHu+5NLjZcmhOpgXnoXjWQgIBW+r1UTZbB2 GEGIA5M5eZdYF+nUXT9aGHwjfZKMhZh6p7EasfxgJiJDES+T896MTBibUgxQSzVKnbxQ PwRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YNELeqsO3ONkBzigACa9WgfAHnyRLEL6gV/TACazJzc=; b=fR8N2L45m3hsik+bLgELB585Der7xf5N9/N3jUFE8nB+cIP8OrXMu0y3oxrDDIDYlN R2KgmkLVltKlxmFYzrnXRupgL6X+K/dBBAISEotUg3AwPDh8JlW7wMg4hOta3H5dnq42 EAw2DV6nOX0P51KGUMpNZlnxFqehA/QvIEr8h0hi8aXMwVVPVspidsZktNzUKpBlJr3m LjdFZ2GjT9D8+pIwricOeQKGHenuW4qXkIQmB+CpabCAtEpdTsp8Hfub5WogV3p9H6pM osrhqZeMZYf5cK7J1gyr6ckGff/Vod3jKwKftITJxRXa6Sf4IRiUPaCVMtpBq6tVwiMA vJPg== X-Gm-Message-State: APjAAAWxX1uMDi3BAHqPwQRYzBjrzlgNbolrfHc9+uBkZtHY6DQBHWvX nSqXNFXBiwwFwGEnMk0EnrlQSr7mW1wcAUfZIMc= X-Google-Smtp-Source: APXvYqznBNXnEw5RZZ4tdgedDsRQHsK/vADIWjCrMTGOLQKAhTXeCoBTP+DgQlTl5assRWvi5M/A6fTORvagJxDrfCU= X-Received: by 2002:a05:600c:230b:: with SMTP id 11mr13181852wmo.85.1561351150527; Sun, 23 Jun 2019 21:39:10 -0700 (PDT) MIME-Version: 1.0 References: <000000000000a7776f058a3ce9db@google.com> <178c7ee0-46b7-8334-ef98-e530eb60a2cf@gmail.com> In-Reply-To: From: Xin Long Date: Mon, 24 Jun 2019 12:38:59 +0800 Message-ID: Subject: Re: KASAN: user-memory-access Read in ip6_hold_safe (3) To: Dmitry Vyukov Cc: David Ahern , syzbot , David Miller , Alexey Kuznetsov , LKML , netdev , syzkaller-bugs , Hideaki YOSHIFUJI Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 3, 2019 at 2:57 PM Dmitry Vyukov wrote: > > On Sat, Jun 1, 2019 at 7:15 PM David Ahern wrote: > > > > On 6/1/19 12:05 AM, syzbot wrote: > > > Hello, > > > > > > syzbot found the following crash on: > > > > > > HEAD commit: dfb569f2 net: ll_temac: Fix compile error > > > git tree: net-next > > syzbot team: > > > > Is there any way to know the history of syzbot runs to determine that > > crash X did not happen at commit Y but does happen at commit Z? That > > narrows the window when trying to find where a regression occurs. > > Hi David, > > All info is available on the dashboard: > > > dashboard link: https://syzkaller.appspot.com/bug?extid=a5b6e01ec8116d046842 > > We don't keep any private info on top of that. > > This crash happened 129 times in the past 9 days. This suggests this > is not a previous memory corruption, these usually happen at most few > times. > The first one was: > > 2019/05/24 15:33 net-next dfb569f2 > > Then it was joined by bpf-next: > > ci-upstream-bpf-next-kasan-gce 2019/06/01 15:51 bpf-next 0462eaac > > Since it happens a dozen of times per day, most likely it was > introduced into net-next around dfb569f2 (syzbot should do new builds > every ~12h, minus broken trees). I think all these pcpu memory corruptions can be marked as Fixed-by: commit c3bcde026684c62d7a2b6f626dc7cf763833875c Author: Xin Long Date: Mon Jun 17 21:34:15 2019 +0800 tipc: pass tunnel dev as NULL to udp_tunnel(6)_xmit_skb