From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: peterx@redhat.com, david@redhat.com,
Andrew Morton <akpm@linux-foundation.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
kernel@collabora.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/2] mm/userfaultfd: add VM_WARN_ONCE()
Date: Mon, 13 Feb 2023 21:31:24 +0500 [thread overview]
Message-ID: <20230213163124.2850816-2-usama.anjum@collabora.com> (raw)
In-Reply-To: <20230213163124.2850816-1-usama.anjum@collabora.com>
Add VM_WARN_ONCE() to uffd_wp_range() to detect range (start, len) abuse.
Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
---
mm/userfaultfd.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
index bccea08005a8..14ec88301511 100644
--- a/mm/userfaultfd.c
+++ b/mm/userfaultfd.c
@@ -716,6 +716,8 @@ void uffd_wp_range(struct mm_struct *dst_mm, struct vm_area_struct *dst_vma,
unsigned int mm_cp_flags;
struct mmu_gather tlb;
+ VM_WARN_ONCE(start < dst_vma->vm_start || start + len > dst_vma->vm_end,
+ "The address range exceeds VMA boundary.\n");
if (enable_wp)
mm_cp_flags = MM_CP_UFFD_WP;
else
--
2.39.1
next prev parent reply other threads:[~2023-02-13 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 16:31 [PATCH v2 1/2] mm/userfaultfd: Support WP on multiple VMAs Muhammad Usama Anjum
2023-02-13 16:31 ` Muhammad Usama Anjum [this message]
2023-02-13 16:54 ` Peter Xu
2023-02-13 17:50 ` Muhammad Usama Anjum
2023-02-13 21:11 ` Peter Xu
2023-02-14 8:49 ` Muhammad Usama Anjum
2023-02-14 21:50 ` Peter Xu
2023-02-15 7:08 ` Muhammad Usama Anjum
2023-02-15 21:45 ` Peter Xu
2023-02-16 6:25 ` Muhammad Usama Anjum
2023-02-16 16:41 ` Peter Xu
2023-02-17 10:59 ` Muhammad Usama Anjum
2023-02-17 16:03 ` Peter Xu
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=20230213163124.2850816-2-usama.anjum@collabora.com \
--to=usama.anjum@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.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