From: David Hildenbrand <david@redhat.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
peterx@redhat.com, Andrew Morton <akpm@linux-foundation.org>
Cc: kernel@collabora.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] mm/userfaultfd: add VM_WARN_ONCE()
Date: Thu, 16 Feb 2023 10:24:50 +0100 [thread overview]
Message-ID: <4d29a9ec-027d-06b9-8543-87d386e58c94@redhat.com> (raw)
In-Reply-To: <20230216091656.2045471-2-usama.anjum@collabora.com>
On 16.02.23 10:16, Muhammad Usama Anjum wrote:
> 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 77c5839e591c..d89ed44d2668 100644
> --- a/mm/userfaultfd.c
> +++ b/mm/userfaultfd.c
> @@ -717,6 +717,8 @@ long uffd_wp_range(struct mm_struct *dst_mm, struct vm_area_struct *dst_vma,
> struct mmu_gather tlb;
> long ret;
>
> + VM_WARN_ONCE(start < dst_vma->vm_start || start + len > dst_vma->vm_end,
> + "The address range exceeds VMA boundary.\n");
VM_WARN_ON_ONCE is sufficient (sorry for spelling out the wrong variant
earlier).
These kinds of bugs are expected to be found early during testing, still
it might make sense to implement a backup path
if (WARN_ON_ONCE(...))
return -EINVAL;
But we can't use VM_WARN_ON_ONCE here, so we can't compile it out
anymore ... so I guess a simple VM_WARN_ON_ONCE() is sufficient.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-02-16 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 9:16 [PATCH v4 1/2] mm/userfaultfd: Support WP on multiple VMAs Muhammad Usama Anjum
2023-02-16 9:16 ` [PATCH v4 2/2] mm/userfaultfd: add VM_WARN_ONCE() Muhammad Usama Anjum
2023-02-16 9:24 ` David Hildenbrand [this message]
2023-02-16 9:48 ` Muhammad Usama Anjum
2023-02-16 20:26 ` Peter Xu
2023-02-17 10:40 ` Muhammad Usama Anjum
2023-02-16 9:37 ` [PATCH v4 1/2] mm/userfaultfd: Support WP on multiple VMAs David Hildenbrand
2023-02-16 20:25 ` Peter Xu
2023-02-17 8:53 ` David Hildenbrand
2023-02-17 17:35 ` 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=4d29a9ec-027d-06b9-8543-87d386e58c94@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=usama.anjum@collabora.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;
as well as URLs for NNTP newsgroup(s).