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=-3.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT 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 1B40BC04AB3 for ; Mon, 27 May 2019 21:11:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E33A121530 for ; Mon, 27 May 2019 21:11:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727193AbfE0VLZ (ORCPT ); Mon, 27 May 2019 17:11:25 -0400 Received: from mga04.intel.com ([192.55.52.120]:23653 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726801AbfE0VLY (ORCPT ); Mon, 27 May 2019 17:11:24 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 May 2019 14:11:24 -0700 X-ExtLoop1: 1 Received: from rpedgeco-mobl.amr.corp.intel.com (HELO localhost.intel.com) ([10.251.0.167]) by orsmga008.jf.intel.com with ESMTP; 27 May 2019 14:11:23 -0700 From: Rick Edgecombe To: linux-kernel@vger.kernel.org, peterz@infradead.org, sparclinux@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org, luto@kernel.org Cc: dave.hansen@intel.com, namit@vmware.com, Rick Edgecombe Subject: [PATCH v5 0/2] Fix issues with vmalloc flush flag Date: Mon, 27 May 2019 14:10:56 -0700 Message-Id: <20190527211058.2729-1-rick.p.edgecombe@intel.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org These two patches address issues with the recently added VM_FLUSH_RESET_PERMS vmalloc flag. Patch 1 addresses an issue that could cause a crash after other architectures besides x86 rely on this path. Patch 2 addresses an issue where in a rare case strange arguments could be provided to flush_tlb_kernel_range(). v4->v5: - Update commit messages with info that the first issue will actually not cause problems today - Avoid re-use of variable (PeterZ) v3->v4: - Drop patch that switched vm_unmap_alias() calls to regular flush (Andy) - Add patch to address correctness previously fixed in dropped patch v2->v3: - Split into two patches (Andy) v1->v2: - Update commit message with more detail - Fix flush end range on !CONFIG_ARCH_HAS_SET_DIRECT_MAP case Rick Edgecombe (2): vmalloc: Fix calculation of direct map addr range vmalloc: Avoid rare case of flushing tlb with weird arguments mm/vmalloc.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) -- 2.20.1