From: Rick Edgecombe <rick.p.edgecombe@intel.com>
To: peterz@infradead.org, linux-mm@kvack.org,
sparclinux@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Cc: dave.hansen@intel.com, namit@vmware.com,
Rick Edgecombe <rick.p.edgecombe@intel.com>
Subject: [PATCH 0/1] Fix for VM_FLUSH_RESET_PERMS on sparc
Date: Fri, 17 May 2019 14:01:22 -0700 [thread overview]
Message-ID: <20190517210123.5702-1-rick.p.edgecombe@intel.com> (raw)
Meelis Roos reported issues with the new VM_FLUSH_RESET_PERMS flag on the sparc
architecture. When freeing many BPF JITs simultaneously, the vfree flush
operations can become stuck waiting as they each try to vm_unmap_aliases().
It also came up that using this flag is not needed for architectures like sparc
that already have normal kernel memory as executable. This patch fixes the usage
of this flag on sparc to also fix it in case the root cause is also an issue on
other architectures. Separately we can disable usage of VM_FLUSH_RESET_PERMS for
these architectures if desired.
Rick Edgecombe (1):
vmalloc: Fix issues with flush flag
mm/vmalloc.c | 23 +++++++++++++----------
1 file changed, 13 insertions(+), 10 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-17 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 21:01 Rick Edgecombe [this message]
2019-05-17 21:01 ` [PATCH 1/1] vmalloc: Fix issues with flush flag Rick Edgecombe
2019-05-20 3:54 ` Edgecombe, Rick P
2019-05-20 19:13 ` 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=20190517210123.5702-1-rick.p.edgecombe@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=bpf@vger.kernel.org \
--cc=dave.hansen@intel.com \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).