Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp341650ybm; Mon, 20 May 2019 17:34:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqyG+61+mdyB/pPHjx3UBFcaTiGMNn3lEIxB/Y0RiXVwrSEX7qyzeZLHDnSLkj0AD4NmOvPu X-Received: by 2002:a63:5c5b:: with SMTP id n27mr79362680pgm.52.1558398886346; Mon, 20 May 2019 17:34:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558398886; cv=none; d=google.com; s=arc-20160816; b=IrzvDq+az/a9150iflPgAScgSjk2buPnjptKL6zmWe2kOD/4kSO7eK6XQQUzbyIC+3 T+tJhYOKjUtC92yLspPxeL/t7u45arEoy1pW0Gdr8kmAZz7GZmu5KSogA/bWiFAOIfo7 rK8WQD+cEy7gg7gb42OsycDkLfE1WDICstdtE5UQDKf0qqFb3HjRgVZnZ4P0YDdghKQD jzk0y6QF5H3tptq3YNZ8EZ35eDdmE3zYkLQl1gYgS5bW+LzPBXWrLBLDEzQ6XFjdjlp1 MvW30+4IARKMEb/r18wXGTAHdF8jklSBXF+BNcVgVuCgqMbTDVtzuT7mfnPGN91f3mwV Sl4w== 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; bh=iqyrGdY5nUcJTAoyQ9D67Ht+r/DpYjgGax4vpXQLUXw=; b=UIKbFrwJ2FDb8wkn94FSUnDjJXr2j0tabHU+usFhUOBCH9YYaGEET5WFQOc3SaqpYw 8TtGerhfBgr0UbOfS8Do0hQee4fU8gstp5xx1yUqxPCw5aq+4rKs6hILTbcDbMhCmFIK +JTJJ6AcHkNWtgPg9blE5hhkcB+3CiMNqphaO0cmpby1wAw93JLQOzrWMB3ijf7G1XTN nHnCVCtZupX+yVFM7R4BYTTtKVYMCCG219hZ2Y+dMtXF5z3GP8So5QnwCC9C+HDhF18A JvIqi0PUgoJn8itowMVLq5YGUMpPTYZ+3Ibag0ZBrJjBhKhLvN8m4RZzeBLMZfn7ZrOR zJ1A== 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 21si20231373pfo.251.2019.05.20.17.34.30; Mon, 20 May 2019 17:34:46 -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 S1727149AbfEUAdW (ORCPT + 99 others); Mon, 20 May 2019 20:33:22 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:59966 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726370AbfEUAdV (ORCPT ); Mon, 20 May 2019 20:33:21 -0400 Received: from localhost (50-78-161-185-static.hfc.comcastbusiness.net [50.78.161.185]) (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 B81BD1400F7CA; Mon, 20 May 2019 17:33:20 -0700 (PDT) Date: Mon, 20 May 2019 20:33:20 -0400 (EDT) Message-Id: <20190520.203320.621504228022195532.davem@davemloft.net> To: rick.p.edgecombe@intel.com Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, linux-mm@kvack.org, mroos@linux.ee, mingo@redhat.com, namit@vmware.com, luto@kernel.org, bp@alien8.de, netdev@vger.kernel.org, dave.hansen@intel.com, sparclinux@vger.kernel.org Subject: Re: [PATCH v2] vmalloc: Fix issues with flush flag From: David Miller In-Reply-To: <3e7e674c1fe094cd8dbe0c8933db18be1a37d76d.camel@intel.com> References: <20190520.154855.2207738976381931092.davem@davemloft.net> <3e7e674c1fe094cd8dbe0c8933db18be1a37d76d.camel@intel.com> X-Mailer: Mew version 6.8 on Emacs 26.1 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]); Mon, 20 May 2019 17:33:21 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Edgecombe, Rick P" Date: Tue, 21 May 2019 00:20:13 +0000 > This behavior shouldn't happen until modules or BPF are being freed. Then that would rule out my theory. The only thing left is whether the permissions are actually set properly. If they aren't we'll take an exception when the BPF program is run and I'm not %100 sure that kernel execute permission violations are totally handled cleanly.