linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: jeffxu@chromium.org
To: akpm@linux-foundation.org, pedro.falcato@gmail.com
Cc: jeffxu@google.com, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, Jeff Xu <jeffxu@chromium.org>
Subject: [PATCH v1 1/1] mseal: Add branch prediction hint.
Date: Tue, 23 Apr 2024 19:28:25 +0000	[thread overview]
Message-ID: <20240423192825.1273679-2-jeffxu@chromium.org> (raw)
In-Reply-To: <20240423192825.1273679-1-jeffxu@chromium.org>

From: Jeff Xu <jeffxu@chromium.org>

It is unlikely that application calls mm syscall, such as mprotect,
on already sealed mappings, adding branch prediction hint.

Signed-off-by: Jeff Xu <jeffxu@chromium.org>
Suggested-by: Pedro Falcato <pedro.falcato@gmail.com>
---
 mm/madvise.c  | 2 +-
 mm/mmap.c     | 4 ++--
 mm/mprotect.c | 2 +-
 mm/mremap.c   | 4 ++--
 mm/mseal.c    | 6 +++---
 5 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/mm/madvise.c b/mm/madvise.c
index f7d589534e82..ea2e4f6981e2 100644
--- a/mm/madvise.c
+++ b/mm/madvise.c
@@ -1442,7 +1442,7 @@ int do_madvise(struct mm_struct *mm, unsigned long start, size_t len_in, int beh
 	 * Check if the address range is sealed for do_madvise().
 	 * can_modify_mm_madv assumes we have acquired the lock on MM.
 	 */
-	if (!can_modify_mm_madv(mm, start, end, behavior)) {
+	if (unlikely(!can_modify_mm_madv(mm, start, end, behavior))) {
 		error = -EPERM;
 		goto out;
 	}
diff --git a/mm/mmap.c b/mm/mmap.c
index 4b80076c319e..6bc0b35ee1f9 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2697,7 +2697,7 @@ int do_vmi_munmap(struct vma_iterator *vmi, struct mm_struct *mm,
 	 * Prevent unmapping a sealed VMA.
 	 * can_modify_mm assumes we have acquired the lock on MM.
 	 */
-	if (!can_modify_mm(mm, start, end))
+	if (unlikely(!can_modify_mm(mm, start, end)))
 		return -EPERM;
 
 	 /* arch_unmap() might do unmaps itself.  */
@@ -3120,7 +3120,7 @@ int do_vma_munmap(struct vma_iterator *vmi, struct vm_area_struct *vma,
 	 * Prevent unmapping a sealed VMA.
 	 * can_modify_mm assumes we have acquired the lock on MM.
 	 */
-	if (!can_modify_mm(mm, start, end))
+	if (unlikely(!can_modify_mm(mm, start, end)))
 		return -EPERM;
 
 	arch_unmap(mm, start, end);
diff --git a/mm/mprotect.c b/mm/mprotect.c
index b30b2494bfcd..465c6cd9578c 100644
--- a/mm/mprotect.c
+++ b/mm/mprotect.c
@@ -748,7 +748,7 @@ static int do_mprotect_pkey(unsigned long start, size_t len,
 	 * checking if memory is sealed.
 	 * can_modify_mm assumes we have acquired the lock on MM.
 	 */
-	if (!can_modify_mm(current->mm, start, end)) {
+	if (unlikely(!can_modify_mm(current->mm, start, end))) {
 		error = -EPERM;
 		goto out;
 	}
diff --git a/mm/mremap.c b/mm/mremap.c
index d69b438dcf83..223552901f14 100644
--- a/mm/mremap.c
+++ b/mm/mremap.c
@@ -912,7 +912,7 @@ static unsigned long mremap_to(unsigned long addr, unsigned long old_len,
 	 *
 	 * can_modify_mm assumes we have acquired the lock on MM.
 	 */
-	if (!can_modify_mm(mm, addr, addr + old_len))
+	if (unlikely(!can_modify_mm(mm, addr, addr + old_len)))
 		return -EPERM;
 
 	if (flags & MREMAP_FIXED) {
@@ -1087,7 +1087,7 @@ SYSCALL_DEFINE5(mremap, unsigned long, addr, unsigned long, old_len,
 	 * Place can_modify_mm here so we can keep the logic related to
 	 * shrink/expand together.
 	 */
-	if (!can_modify_mm(mm, addr, addr + old_len)) {
+	if (unlikely(!can_modify_mm(mm, addr, addr + old_len))) {
 		ret = -EPERM;
 		goto out;
 	}
diff --git a/mm/mseal.c b/mm/mseal.c
index daadac4b8125..bf783bba8ed0 100644
--- a/mm/mseal.c
+++ b/mm/mseal.c
@@ -32,7 +32,7 @@ static inline void set_vma_sealed(struct vm_area_struct *vma)
  */
 static bool can_modify_vma(struct vm_area_struct *vma)
 {
-	if (vma_is_sealed(vma))
+	if (unlikely(vma_is_sealed(vma)))
 		return false;
 
 	return true;
@@ -75,7 +75,7 @@ bool can_modify_mm(struct mm_struct *mm, unsigned long start, unsigned long end)
 
 	/* going through each vma to check. */
 	for_each_vma_range(vmi, vma, end) {
-		if (!can_modify_vma(vma))
+		if (unlikely(!can_modify_vma(vma)))
 			return false;
 	}
 
@@ -100,7 +100,7 @@ bool can_modify_mm_madv(struct mm_struct *mm, unsigned long start, unsigned long
 
 	/* going through each vma to check. */
 	for_each_vma_range(vmi, vma, end)
-		if (is_ro_anon(vma) && !can_modify_vma(vma))
+		if (unlikely(is_ro_anon(vma) && !can_modify_vma(vma)))
 			return false;
 
 	/* Allow by default. */
-- 
2.44.0.769.g3c40516874-goog



      reply	other threads:[~2024-04-23 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 19:28 [PATCH v1 0/1] " jeffxu
2024-04-23 19:28 ` jeffxu [this message]

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=20240423192825.1273679-2-jeffxu@chromium.org \
    --to=jeffxu@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=jeffxu@google.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pedro.falcato@gmail.com \
    /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