From: Linus Torvalds <torvalds@linux-foundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-mm <linux-mm@kvack.org>,
open list <linux-kernel@vger.kernel.org>,
Song Liu <song@kernel.org>,
Muchun Song <songmuchun@bytedance.com>,
Christoph Hellwig <hch@lst.de>, Vlastimil Babka <vbabka@suse.cz>,
David Hildenbrand <david@redhat.com>,
Rik van Riel <riel@surriel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: page_alloc.c:(.init.text+0xa7c): undefined reference to `vmalloc_huge'
Date: Mon, 25 Apr 2022 01:28:01 -0700 [thread overview]
Message-ID: <CAHk-=wgZ9H_Cama8RNyqNbPB5ydFy4P319JUcz9E27GyZ1xqdw@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYscb1y4a17Sf5G_Aibt+WuSf-ks_Qjw9tYFy=A4sjCEug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
On Mon, Apr 25, 2022 at 1:10 AM Naresh Kamboju
<naresh.kamboju@linaro.org> wrote:
>
> # CONFIG_MMU is not set
I just sent the stupid and straightforward patch in
https://lore.kernel.org/all/CAHk-=wi5DYKbFE4j-jC2HGsKVuf1RpZbEiYt4tSXuxGKiN9oJg@mail.gmail.com/
but then I thought maybe the alias patch is as simple as the attached.
So does either (or both) of these patches work?
Linus
[-- Attachment #2: patch.diff --]
[-- Type: text/x-patch, Size: 407 bytes --]
mm/nommu.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/nommu.c b/mm/nommu.c
index 55a9e48a7a02..9d7afc2d959e 100644
--- a/mm/nommu.c
+++ b/mm/nommu.c
@@ -226,6 +226,8 @@ void *vmalloc(unsigned long size)
}
EXPORT_SYMBOL(vmalloc);
+void *vmalloc_huge(unsigned long size, gfp_t gfp_mask) __weak __alias(__vmalloc);
+
/*
* vzalloc - allocate virtually contiguous memory with zero fill
*
next prev parent reply other threads:[~2022-04-25 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:10 Naresh Kamboju
2022-04-25 8:28 ` Linus Torvalds [this message]
2022-04-25 8:44 ` Naresh Kamboju
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='CAHk-=wgZ9H_Cama8RNyqNbPB5ydFy4P319JUcz9E27GyZ1xqdw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naresh.kamboju@linaro.org \
--cc=riel@surriel.com \
--cc=song@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=vbabka@suse.cz \
/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