From: Andrew Morton <akpm@linux-foundation.org>
To: Hsin-Hui Wu <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: Wed, 4 Nov 2020 10:19:01 -0800 [thread overview]
Message-ID: <20201104101901.b9750cc1a4413bc8fdc17239@linux-foundation.org> (raw)
In-Reply-To: <CANpob6KFd96g+KtDV81+25bu3cZwkfXK6F+EMC9zhbXmDhmRdQ@mail.gmail.com>
On Wed, 4 Nov 2020 08:55:11 -0500 Hsin-Hui Wu <hsinhuiwu@gmail.com> wrote:
> > 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?
>
> [Frank] The Dell PowerEdge R740/R940 can have up to 3TB/6TB memory.
> installed. Our application requires reserve consecutive memory in the kernel
> space and protected from userspace programs.
Did this require custom kernel changes? If not, precisely which system
calls were used to cause this allocation attempt?
> ----------------------------------------------------------------------------------------------------
> OK, thanks. Against current mainline your proposed change would look
> like this, yes?
>
> [Frank] Yes. This will support up to less than 16 TB. If you want to support
> more than 16 TB, we need to expand nr_pages to unsigned long as
> Matthew pointed out.
>
> Will it be possible to add this to kernel 3.10.0-957.27.2.el7.x86_64?
That is up to Red Hat to decide.
next prev parent reply other threads:[~2020-11-04 18:19 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
2020-11-04 0:47 ` Matthew Wilcox
2020-11-04 13:55 ` Hsin-Hui Wu
2020-11-04 18:19 ` Andrew Morton [this message]
[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=20201104101901.b9750cc1a4413bc8fdc17239@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