From: Peter Zijlstra <peterz@infradead.org>
To: Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org, luto@kernel.org,
dave.hansen@intel.com, namit@vmware.com
Subject: Re: [PATCH v5 0/2] Fix issues with vmalloc flush flag
Date: Tue, 28 May 2019 10:01:49 +0200 [thread overview]
Message-ID: <20190528080149.GJ2623@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190527211058.2729-1-rick.p.edgecombe@intel.com>
On Mon, May 27, 2019 at 02:10:56PM -0700, Rick Edgecombe wrote:
> 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().
Thanks!
next prev parent reply other threads:[~2019-05-28 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 21:10 Rick Edgecombe
2019-05-27 21:10 ` [PATCH v5 1/2] vmalloc: Fix calculation of direct map addr range Rick Edgecombe
2019-05-27 21:10 ` [PATCH v5 2/2] vmalloc: Avoid rare case of flushing tlb with weird arguments Rick Edgecombe
2019-05-28 8:01 ` Peter Zijlstra [this message]
2019-05-29 0:23 ` [PATCH v5 0/2] Fix issues with vmalloc flush flag David Miller
2019-05-29 5:11 ` Edgecombe, Rick P
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=20190528080149.GJ2623@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=rick.p.edgecombe@intel.com \
--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