From: Rick Edgecombe <rick.p.edgecombe@intel.com>
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 <rick.p.edgecombe@intel.com>
Subject: [PATCH v4 0/2] Fix issues with vmalloc flush flag
Date: Tue, 21 May 2019 13:51:35 -0700 [thread overview]
Message-ID: <20190521205137.22029-1-rick.p.edgecombe@intel.com> (raw)
These two patches address issues with the recently added
VM_FLUSH_RESET_PERMS vmalloc flag.
Patch 1 is the most critical and addresses an issue that could cause a
crash on x86.
Patch 2 addresses an issue where in a rare case strange arguments
could be provided to flush_tlb_kernel_range(). Most arch's should be
fine with it, but some may not like them, so we should avoid doing
this.
v3->v4:
- Drop patch that switched vm_unmap_alias() calls to regular flush
- Add patch to address correctness previously fixed in dropped patch
v2->v3:
- Split into two patches
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 arguements
mm/vmalloc.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2019-05-21 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:51 Rick Edgecombe [this message]
2019-05-21 20:51 ` [PATCH v4 1/2] vmalloc: Fix calculation of direct map addr range Rick Edgecombe
2019-05-27 12:20 ` Peter Zijlstra
2019-05-27 20:05 ` Edgecombe, Rick P
2019-05-21 20:51 ` [PATCH v4 2/2] vmalloc: Avoid rare case of flushing tlb with weird arguements Rick Edgecombe
2019-05-27 12:24 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190521205137.22029-1-rick.p.edgecombe@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=namit@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox