Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp2616984imm; Sun, 24 Jun 2018 00:18:45 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLDzwL4/Rrmx0tZY77XvFn/3AbUm2EhtAlMP/DbTWoxfb7sr2vMt89cdJdG0ySiJ0AQXMaN X-Received: by 2002:a17:902:6945:: with SMTP id k5-v6mr7767211plt.175.1529824725902; Sun, 24 Jun 2018 00:18:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529824725; cv=none; d=google.com; s=arc-20160816; b=HELPOCZkDporHx1w9M1hWXEkjibgJvor6ZzUnOCBRAyZEsrDazhKiTi6eFsC5k6Shg ANTnT9xV6TYWW5McR2+lyHRPV5jOrDtuBLHi4fop7f2G7QJADU062hT3foJwTo4OYEGJ Zg2CPPYUgR52EMP1K+df2b68tZyIsS/J9Sa8pkyZGktbhZCEQkczs2Cj3y4RevSNUd8F kRe106sVPpkyzWcClsPSdd5waxWDPEEYhaUfX9CeUP4s2w1eFyDx+EsxhAUiTE06g7hK yrunzhjxouYaL+GQcB4miPloSH/TJooU4rE1/367BGdNP2DspRfKUEuqBULhEUz4cIBv 2U3w== 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:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=1l0wlOXk0AbgRfVca5sT+bvQTAcnaUnsTrJb3WdY4x8=; b=ujVjgDq5h03URo+kqb3M4DyUvaGlzE7Ha5STxYhLngPkEkrAHBNF8vXxKSQHp/pvQT u6FVq34QZ84YSbIX+JHCyxgFrSnGqq/A+GnTeYP6SDSIrCMrR64k2RMehSKgHSYjT47Z 85afLHhm3+rxpnqGeoUaHZP4u+hQ2Ip5Fq3r2rnoYmY4YYTeolWYnooehhcYREu6Jti1 B7+p7LaJa4ypZSMQVaVmpyU/FYVtaFbVgyRaCUHSwmrFUrZPs4+S6D3OvzjmQJzDNMIv NeUOZW7tWYW6JBh0cvK95cNXwQTX/IKJaBa8KiV1vDYQcikH//Jg2+urCFM/t/Dp8IWH Hr7A== 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 i12-v6si9472018pgp.325.2018.06.24.00.18.31; Sun, 24 Jun 2018 00:18: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 S1751851AbeFXHR3 (ORCPT + 99 others); Sun, 24 Jun 2018 03:17:29 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:60418 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751714AbeFXHR1 (ORCPT ); Sun, 24 Jun 2018 03:17:27 -0400 Received: from localhost (unknown [211.196.191.92]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id E93F913D398E2; Sun, 24 Jun 2018 00:17:21 -0700 (PDT) Date: Sun, 24 Jun 2018 16:14:11 +0900 (KST) Message-Id: <20180624.161411.1560796210597132716.davem@davemloft.net> To: tglx@linutronix.de Cc: syzbot+a4eb8c7766952a1ca872@syzkaller.appspotmail.com, ast@kernel.org, daniel@iogearbox.net, hpa@zytor.com, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org, mingo@redhat.com, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com, x86@kernel.org, yoshfuji@linux-ipv6.org, peterz@infradead.org Subject: Re: BUG: unable to handle kernel paging request in bpf_int_jit_compile From: David Miller In-Reply-To: References: <000000000000d48c8e056f5b6c67@google.com> X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Sun, 24 Jun 2018 00:17:27 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Thomas Gleixner Date: Sun, 24 Jun 2018 09:09:09 +0200 (CEST) > I'm really tempted to make the BPF config switch depend on BROKEN. This really isn't necessary Thomas. Whoever wrote the code didn't understand that set ro can legitimately fail. So let's correct that instead of flaming a feature. Thank you.