Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4255236imm; Mon, 20 Aug 2018 12:31:45 -0700 (PDT) X-Google-Smtp-Source: AA+uWPz97xTUtHagNt1ijbvL6tCo7pLwor04Yfj0vSov/5C7t0BLB2BkqZLYwsG36W64yCZJ0Dzv X-Received: by 2002:a65:5284:: with SMTP id y4-v6mr43229116pgp.283.1534793505209; Mon, 20 Aug 2018 12:31:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534793505; cv=none; d=google.com; s=arc-20160816; b=Ak/w2I6jbZRfkZbXcUuSZ0YnX+nxxFLGAGTBHKYCgNExsscZvJdgtS2pqi7U/OM3xW t4cyrVKiMYraNXzrzMKaLbAVgwyx2SNv0erRzxXkZZWmAJ5XjUIiSswRzci5KTelGHWv 1xC2Tb5+5m6H3OK9LRIccTSFzmVFzmWqrFQOFZrhDfudCHBFSKF5YczIDhRNJh1fBK0T anv9M4BQLihT2+0WRnNZ6GWriT7botgHKS/MKO15bKoBunEEEy9Bxm8m0Pccr3nbocwf HbYISCW4YpoJ5fgaZPtmskybzV9s/8C1DafQG/Ov1P3M/XUc4bOLpLPNSVOFZ4aR9bmB 0Qjg== 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=/qeF9WcZ2DcrgD48z06ueZHfTZPurijftRA1lfEAUhc=; b=wlP34amD3n2P9y9nsKN0MiwKwVs589DNiAOM6qxIGK+geIp3EroSVrlA+9m5OtfTNe ZQ08ROP7+2ZcE2iAFNF3dent1sbWTRM7GFIuJyJ9d4bhxZRYCn1+r8/FVK+32/RFiMdZ bdJwrY6Men8al9wkOEF4oCaFZg5AIj3MaOxqK4OLpv/3/XelQJd1w+3KlNd9WfL1XurR Vp9WaUPNK5lBWmZgnCt+gHD9oaJM+SJ7A04b1Shz4NoP0iYrADFasdQ0M0HmlFE++Xfu ndau9D76xMTxizZDDeq7I/Fb4VJOXQWRziNXrFVKsGWZioqlftVFWVjgTY0P9IVBl/SU KCcA== 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 t9-v6si10321804pgr.244.2018.08.20.12.31.30; Mon, 20 Aug 2018 12:31:45 -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 S1726634AbeHTWqk (ORCPT + 99 others); Mon, 20 Aug 2018 18:46:40 -0400 Received: from www62.your-server.de ([213.133.104.62]:51194 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726077AbeHTWqj (ORCPT ); Mon, 20 Aug 2018 18:46:39 -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 1frps1-0007Ph-SY; Mon, 20 Aug 2018 21:29:45 +0200 Received: from [178.197.248.15] (helo=linux.home) by sslproxy05.your-server.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1frps1-0004gX-NY; Mon, 20 Aug 2018 21:29:45 +0200 Subject: Re: Allocation failure with subsequent kernel crash To: whiteheadm@acm.org, Alexei Starovoitov Cc: LKML , Network Development , Ingo Molnar , Thomas Gleixner , Alexei Starovoitov References: From: Daniel Borkmann Message-ID: <05825446-e8aa-a983-3fc6-4dc8e81cba57@iogearbox.net> Date: Mon, 20 Aug 2018 21:29:45 +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.1/24860/Mon Aug 20 18:47:04 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Matthew, On 08/20/2018 08:03 AM, tedheadster wrote: > On Mon, Aug 20, 2018 at 1:22 AM, Alexei Starovoitov > wrote: >> I don't remember vzalloc issues that was fixed in this area. >> 4.14 kernel is quite old. Since then syzbot found few mem >> related bugs that were fixed. >> please try to reproduce on the latest tree. > > Alexei, > I get this panic with two very recent kernels: 4.18.0 and 4.17.14. I > do not think this has been fixed. I am still trying to bisect it, but > sometimes it takes 5 hours for the panic to occur. I've been looking into it a bit today and still am. Given you've seen this on x86_32 and also on older kernels, I presume JIT was not involved (/proc/sys/net/core/bpf_jit_enable is 0). Do you run any specific workload until you trigger this (e.g. fuzzer on BPF), or any specific event that triggers at that time after ~5hrs? Or only systemd on idle machine? Have you managed to reproduce this also elsewhere? Bisect seems indeed painful but would help tremendously; perhaps also dumping the BPF insns that are loaded at that point in time. Thanks a lot, Daniel > - Matthew Whitehead >