From: Andrew Morton <akpm@linux-foundation.org>
To: hsinhuiwu@gmail.com
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: Re: [Bug 210023] New: Crash when allocating > 2 TB memory
Date: Tue, 3 Nov 2020 16:27:40 -0800 [thread overview]
Message-ID: <20201103162740.6a7c835276b5a704d5b219cc@linux-foundation.org> (raw)
In-Reply-To: <bug-210023-27@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 03 Nov 2020 18:50:07 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=210023
>
> Bug ID: 210023
> Summary: Crash when allocating > 2 TB memory
> Product: Memory Management
> Version: 2.5
> Kernel Version: 3.10.0-957.27.2.el7.x86_64
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: blocking
> Priority: P1
> Component: Slab Allocator
> Assignee: akpm@linux-foundation.org
> Reporter: hsinhuiwu@gmail.com
> Regression: No
>
> With a machine with 3 TB (more than 2 TB memory). If you use vmalloc to
> allocate > 2 TB memory, the array_size below will be overflowed.
How was this observed?
Is there any know userspace operation which causes the kernel to try to
vmalloc such a large hunk of memory?
> The array_size is an unsigned int and can only be used to allocate less than 2
> TB memory. If you pass 2*1028*1028*1024*1024 = 2 * 2^40 in the argument of
> vmalloc. The array_size will become 2*2^31 = 2^32. The 2^32 cannot be store
> with a 32 bit integer.
>
> The fix is to change the type of array_size to unsigned long.
>
> vmalloc.c
>
> 1762 void *vmalloc(unsigned long size)
> 1763 {
> 1764 return __vmalloc_node_flags(size, NUMA_NO_NODE,
> 1765 GFP_KERNEL | __GFP_HIGHMEM);
> 1766 }
OK, thanks. Against current mainline your proposed change would look
like this, yes?
--- a/mm/vmalloc.c~a
+++ a/mm/vmalloc.c
@@ -2461,9 +2461,11 @@ static void *__vmalloc_area_node(struct
{
const gfp_t nested_gfp = (gfp_mask & GFP_RECLAIM_MASK) | __GFP_ZERO;
unsigned int nr_pages = get_vm_area_size(area) >> PAGE_SHIFT;
- unsigned int array_size = nr_pages * sizeof(struct page *), i;
+ unsigned long array_size
+ unsigned int i;
struct page **pages;
+ array_size = (unsigned long)nr_pages * sizeof(struct page *);
gfp_mask |= __GFP_NOWARN;
if (!(gfp_mask & (GFP_DMA | GFP_DMA32)))
gfp_mask |= __GFP_HIGHMEM;
_
next parent reply other threads:[~2020-11-04 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-210023-27@https.bugzilla.kernel.org/>
2020-11-04 0:27 ` Andrew Morton [this message]
2020-11-04 0:47 ` Matthew Wilcox
2020-11-04 13:55 ` Hsin-Hui Wu
2020-11-04 18:19 ` Andrew Morton
[not found] ` <CANpob6LY6oXqTG0GTJk-Z9qJtp9kpCCdoDAsbOJgTA8QfPCe2Q@mail.gmail.com>
[not found] ` <20201104163822.95df9ee4e42ad5ec45852a19@linux-foundation.org>
2020-11-05 3:52 ` Hsin-Hui Wu
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=20201103162740.6a7c835276b5a704d5b219cc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hsinhuiwu@gmail.com \
--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