From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Dinh Nguyen <dinguyen@kernel.org>,
Jarkko Sakkinen <jarkko@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
<linux-sgx@vger.kernel.org>, <amd-gfx@lists.freedesktop.org>,
<linux-mm@kvack.org>, Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH 3/5] mm: mprotect: use VM_ACCESS_FLAGS
Date: Wed, 19 Oct 2022 11:49:43 +0800 [thread overview]
Message-ID: <20221019034945.93081-4-wangkefeng.wang@huawei.com> (raw)
In-Reply-To: <20221019034945.93081-1-wangkefeng.wang@huawei.com>
Simplify VM_READ|VM_WRITE|VM_EXEC with VM_ACCESS_FLAGS.
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
---
mm/mprotect.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/mprotect.c b/mm/mprotect.c
index 668bfaa6ed2a..99762403cc8f 100644
--- a/mm/mprotect.c
+++ b/mm/mprotect.c
@@ -756,8 +756,7 @@ static int do_mprotect_pkey(unsigned long start, size_t len,
* If a permission is not passed to mprotect(), it must be
* cleared from the VMA.
*/
- mask_off_old_flags = VM_READ | VM_WRITE | VM_EXEC |
- VM_FLAGS_CLEAR;
+ mask_off_old_flags = VM_ACCESS_FLAGS | VM_FLAGS_CLEAR;
new_vma_pkey = arch_override_mprotect_pkey(vma, prot, pkey);
newflags = calc_vm_prot_bits(prot, new_vma_pkey);
--
2.35.3
next prev parent reply other threads:[~2022-10-19 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 3:49 [PATCH 0/5] mm: cleanup with VM_ACCESS_FLAGS Kefeng Wang
2022-10-19 3:49 ` [PATCH 1/5] nios2: remove unused INIT_MMAP Kefeng Wang
2022-10-19 3:49 ` [PATCH 2/5] x86/sgx: use VM_ACCESS_FLAGS Kefeng Wang
2022-10-23 20:07 ` Jarkko Sakkinen
2022-10-23 20:09 ` Jarkko Sakkinen
2022-10-19 3:49 ` Kefeng Wang [this message]
2022-10-19 3:49 ` [PATCH 4/5] mm: debug_vm_pgtable: " Kefeng Wang
2022-10-19 3:49 ` [PATCH 5/5] amdgpu: " Kefeng Wang
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=20221019034945.93081-4-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dave.hansen@linux.intel.com \
--cc=dinguyen@kernel.org \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sgx@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).