From: David Hildenbrand <david@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>, Will Deacon <will@kernel.org>
Cc: andreyknvl@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Mel Gorman <mgorman@suse.de>,
keescook@chromium.org
Subject: Re: [PATCH] mm/vmalloc: Don't allow VM_NO_GUARD on vmap()
Date: Thu, 16 Sep 2021 14:34:35 +0200 [thread overview]
Message-ID: <9fead1ff-868c-bddd-326b-a5b3eeeb9faf@redhat.com> (raw)
In-Reply-To: <YUMfdA36fuyZ+/xt@hirez.programming.kicks-ass.net>
On 16.09.21 12:41, Peter Zijlstra wrote:
>
> The vmalloc guard pages are added on top of each allocation, thereby
> isolating any two allocations from one another. The top guard of the
> lower allocation is the bottom guard guard of the higher allocation
> etc.
>
> Therefore VM_NO_GUARD is dangerous; it breaks the basic premise of
> isolating separate allocations.
>
> There are only two in-tree users of this flag, neither of which use it
> through the exported interface. Ensure it stays this way.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> include/linux/vmalloc.h | 2 +-
> mm/vmalloc.c | 7 +++++++
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/vmalloc.h b/include/linux/vmalloc.h
> index 671d402c3778..10e9571ff0b2 100644
> --- a/include/linux/vmalloc.h
> +++ b/include/linux/vmalloc.h
> @@ -22,7 +22,7 @@ struct notifier_block; /* in notifier.h */
> #define VM_USERMAP 0x00000008 /* suitable for remap_vmalloc_range */
> #define VM_DMA_COHERENT 0x00000010 /* dma_alloc_coherent */
> #define VM_UNINITIALIZED 0x00000020 /* vm_struct is not fully initialized */
> -#define VM_NO_GUARD 0x00000040 /* don't add guard page */
> +#define VM_NO_GUARD 0x00000040 /* ***DANGEROUS*** don't add guard page */
> #define VM_KASAN 0x00000080 /* has allocated kasan shadow memory */
> #define VM_FLUSH_RESET_PERMS 0x00000100 /* reset direct map and flush TLB on unmap, can't be freed in atomic context */
> #define VM_MAP_PUT_PAGES 0x00000200 /* put pages and free array in vfree */
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index d77830ff604c..01927ebea267 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2743,6 +2743,13 @@ void *vmap(struct page **pages, unsigned int count,
>
> might_sleep();
>
> + /*
> + * Your top guard is someone else's bottom guard. Not having a top
> + * guard compromises someone else's mappings too.
> + */
> + if (WARN_ON_ONCE(flags & VM_NO_GUARD))
> + flags &= ~VM_NO_GUARD;
> +
> if (count > totalram_pages())
> return NULL;
>
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-09-16 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 10:41 Peter Zijlstra
2021-09-16 11:23 ` Christoph Hellwig
2021-09-16 12:34 ` David Hildenbrand [this message]
2021-09-16 13:30 ` Will Deacon
2021-09-16 15:57 ` Kees Cook
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=9fead1ff-868c-bddd-326b-a5b3eeeb9faf@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=hch@lst.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=will@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