linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Cc: Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 4/5] mm/vmalloc: remove unmap_kernel_range
Date: Fri, 02 Apr 2021 01:58:00 +1000	[thread overview]
Message-ID: <1617292598.m6g0knx24s.astroid@bobo.none> (raw)
In-Reply-To: <20210322021806.892164-5-npiggin@gmail.com>

Excerpts from Nicholas Piggin's message of March 22, 2021 12:18 pm:
> This is a shim around vunmap_range, get rid of it.
> 
> Move the main API comment from the _noflush variant to the normal
> variant, and make _noflush internal to mm/.

This requires a fix for nommu builds and a comment bug that sfr noticed.

---

Fix for "mm/vmalloc: remove unmap_kernel_range"

Fixes:

mm/vmalloc.c:425: warning: expecting prototype for vunmap_range_noflush().
Prototype was for vunmap_range() instead

percpu.c:undefined reference to `vunmap_range_noflush` on NOMMU builds

Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
 mm/internal.h | 3 +++
 mm/vmalloc.c  | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/mm/internal.h b/mm/internal.h
index 8b20d5039b74..217fff7c7807 100644
--- a/mm/internal.h
+++ b/mm/internal.h
@@ -632,6 +632,9 @@ int vmap_pages_range_noflush(unsigned long addr, unsigned long end,
 {
 	return -EINVAL;
 }
+static inline void vunmap_range_noflush(unsigned long start, unsigned long end)
+{
+}
 #endif
 
 #endif	/* __MM_INTERNAL_H */
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 5423f6c1417f..f99c1bf714cd 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -413,7 +413,7 @@ void vunmap_range_noflush(unsigned long start, unsigned long end)
 }
 
 /**
- * vunmap_range_noflush - unmap kernel virtual addresses
+ * vunmap_range - unmap kernel virtual addresses
  * @addr: start of the VM area to unmap
  * @end: end of the VM area to unmap (non-inclusive)
  *
-- 
2.23.0



      parent reply	other threads:[~2021-04-01 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210322021806.892164-1-npiggin@gmail.com>
     [not found] ` <20210322021806.892164-2-npiggin@gmail.com>
2021-04-01 15:56   ` [PATCH v2 1/5] mm/vmalloc: remove map_kernel_range Nicholas Piggin
     [not found] ` <20210322021806.892164-5-npiggin@gmail.com>
2021-04-01 15:58   ` Nicholas Piggin [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=1617292598.m6g0knx24s.astroid@bobo.none \
    --to=npiggin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-mm@kvack.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).