Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp727598imm; Mon, 9 Jul 2018 09:32:03 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcgfSc41fJg6N6lA0lzVb8EZbNhKeQ8zlBihv/QYY39H/Mj+AEOQahR9m0ZgZS6O7PONskD X-Received: by 2002:a62:998:: with SMTP id 24-v6mr20164181pfj.99.1531153923840; Mon, 09 Jul 2018 09:32:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531153923; cv=none; d=google.com; s=arc-20160816; b=FJGSrDlVns6wEXRG4g6L2jyzezZCfVtfRIR5/5xIF6+rQs4TZuexe+MCA8cw+rVqZq cDpzdZcRLVPQ41rshtfJxdTAufZPrN/Ve4i3GtaZdK+RYM9ovK7+pJlfEIi/yC/5bsF1 yVKIPJWvToGJyHh4cxDYppb+kPrVHkWKppTv11wd00ko1JZtgGfvvQm/ZaI+11rcaPKH KySSRIejfIkVWTI6ahfskVcErS8Azy5vshrQOxGRBS8xWOS94ifYC78NgKSEYw8LzyGI T7LS4k/oKPwx9KAygY9hD6DAc/6ORgBYBRH48TC/yst+VdH0oCGMhZHUE6KCyDezwV7G hqgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=4vw8c62aI0e1WkhNMurx7MA6+0v6U3zO2yrleWskhl4=; b=cKf8cMhke502vljqcAR5YFxrkkjLPv8xR6BQ+H3PJJmxQsXuD2+P/14YHsNEIrpW4O 7hkrAlvx0zhW9YRi10ll6gasm33B8ekR26bnU4v1D+dWxppJgo35zT/WLMm1I2XyObFg mf8jGkzkTaD6icNgx1JyhnoUr0o+3jF/rYbnFj0YlaPnCLFsUM/woEdQdMq2r9yFCCq9 T/c76pHYoKt79W1ig7P/A9QIeCNdOJiqDvwGL0D9WutBBi6P+me3eHbU+Nk6eq4qw6m3 2Lr6d4Fzxxf1SP1wsZX7EzeKeSDvmHgSCGyfcUtk/JlmuzuBgBmxbbmMVH0XQUOgrEmZ 21MA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i5-v6si14109188pgc.351.2018.07.09.09.31.49; Mon, 09 Jul 2018 09:32:03 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933372AbeGIQay (ORCPT + 99 others); Mon, 9 Jul 2018 12:30:54 -0400 Received: from www62.your-server.de ([213.133.104.62]:49102 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932845AbeGIQax (ORCPT ); Mon, 9 Jul 2018 12:30:53 -0400 Received: from [78.46.172.2] (helo=sslproxy05.your-server.de) by www62.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85_2) (envelope-from ) id 1fcZ3n-0000kI-PK; Mon, 09 Jul 2018 18:30:47 +0200 Received: from [62.203.87.61] (helo=linux.home) by sslproxy05.your-server.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1fcZ3n-000DUm-Kc; Mon, 09 Jul 2018 18:30:47 +0200 Subject: Re: kernel BUG at mm/slab.c:LINE! (2) To: Dmitry Vyukov , Christopher Lameter , Alexei Starovoitov , netdev Cc: syzbot , Kees Cook , LKML , Linux-MM , syzkaller-bugs References: <000000000000afa87d05708af289@google.com> <010001647fcab0b9-1154d4da-94f8-404e-8898-b8acdf366592-000000@email.amazonses.com> From: Daniel Borkmann Message-ID: <35087252-a5fa-c162-efb2-aa2b6a30515a@iogearbox.net> Date: Mon, 9 Jul 2018 18:30:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net X-Virus-Scanned: Clear (ClamAV 0.100.0/24737/Mon Jul 9 14:40:44 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/09/2018 06:16 PM, Dmitry Vyukov wrote: > On Mon, Jul 9, 2018 at 6:05 PM, Christopher Lameter wrote: >> On Sun, 8 Jul 2018, syzbot wrote: >> >>> kernel BUG at mm/slab.c:4421! >> >> Classic location that indicates memory corruption. Can we rerun this with >> CONFIG_SLAB_DEBUG? Alternatively use SLUB debugging for better debugging >> without rebuilding. > > This runs with KASAN which is way more powerful than slab/slub debug. > > There two other recent crashes in bpf_test_finish which has more info: > > https://syzkaller.appspot.com/bug?id=f831c88feddf5f4de09b846bbe53e5b8c06e5c02 > https://syzkaller.appspot.com/bug?id=059cee5623ce519359e7440ba6d0d6af8b82694e Fyi, looking into the two today as well.