From: Shubhang <sh@gentwo.org>
To: Dev Jain <dev.jain@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
Shubhang Kaushik <shubhang@os.amperecomputing.com>,
"Christoph Lameter (Ampere)" <cl@gentwo.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc: reject overflowing vm_map_ram page counts
Date: Fri, 23 Oct 2026 00:37:00 -0700 (PDT) [thread overview]
Message-ID: <b003613a-42ff-b789-5154-9a3208ee246a@gentwo.org> (raw)
In-Reply-To: <18c9c7bd-0d89-45dd-8425-64f10e83fbb1@arm.com>
Hi Dev,
On Fri, 23 Oct 2026, Dev Jain wrote:
>
>
> On 23/10/26 5:05 am, Shubhang Kaushik (Ampere) wrote:
>> vm_map_ram() converts its unsigned int page count to an unsigned long
>> byte size without checking for overflow.
>>
>> On 32-bit kernels, a count greater than ULONG_MAX >> PAGE_SHIFT wraps
>> the byte size. vm_map_ram() passes that size to both alloc_vmap_area()
>> and vmap_pages_range(), so it can allocate and map only the wrapped
>> number of pages while returning success for the original larger request.
>
> I would expect the caller to take care of this?
>
> In vmap(), the check is count > totalram_pages(), is this check more
> appropriate to be used in vm_map_ram too?
>
Thanks for the review. I have addressed the conversion issue in v2
with check_mul_overflow(), as suggested by Andrew:
https://lore.kernel.org/lkml/20261022-vmalloc-reject-overflow-v2-1-0db7a20c53f0@gentwo.org/
I do not think the totalram_pages() check in vmap() is an appropriate
replacement for the overflow check in vm_map_ram(). It is a separate
sanity check on the requested page count; it does not ensure that
count * PAGE_SIZE is representable in an unsigned long.
For example, on a 32-bit PAE kernel, totalram_pages() can exceed
ULONG_MAX >> PAGE_SHIFT, so a count can pass that check while its byte
size still overflows.
vm_map_ram() is also a separate API and performs this conversion itself,
so the check_mul_overflow() validation should remain.
Regards,
Shubhang Kaushik
next prev parent reply other threads:[~2026-10-23 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 23:35 Shubhang Kaushik (Ampere)
2026-10-23 3:19 ` Andrew Morton
2026-10-23 6:12 ` Shubhang
2026-10-23 6:54 ` Dev Jain
2026-10-23 7:37 ` Shubhang [this message]
2026-10-23 11:22 ` Anshuman Khandual
2026-10-23 17:02 ` Shubhang
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=b003613a-42ff-b789-5154-9a3208ee246a@gentwo.org \
--to=sh@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=shubhang@os.amperecomputing.com \
--cc=urezki@gmail.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
all inboxes | Powered by JetHome®