From: Hugh Dickins <hugh@veritas.com>
To: Anatoli Antonovitch <antonovi@ati.com>
Cc: Willy Tarreau <w@1wt.eu>, Tigran Aivazian <tigran@veritas.com>,
Michael Chen <micche@ati.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]i386: fix overflow in vmap on an x86 system which has more than 4GB memory.
Date: Sat, 23 Sep 2006 18:26:26 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0609231759590.30885@blonde.wat.veritas.com> (raw)
In-Reply-To: <1158334477.5219.1.camel@antonovi-desktop>
This is a 2.4 fix (not needed in 2.6): let's CC maintainer Willy Tarreau.
On Fri, 15 Sep 2006, Anatoli Antonovitch wrote:
> Description
> (max_mapnr << PAGE_SHIFT) would overflow on an x86 system which has more
> than 4GB memory, and hence cause vmap to fail every time.
Good point, thanks for the patch. Sorry I'm so slow to get to it.
>
> Signed-off-by: Michael Chen <micche@ati.com>
>
> Patch
> diff -Nur linux-2.4.21-40.EL/mm/vmalloc.c
> linux-2.4.21-40.EL.diff/mm/vmalloc.c
> --- linux-2.4.21-40.EL/mm/vmalloc.c 2006-02-02 21:13:20.000000000
> -0600
> +++ linux-2.4.21-40.EL.diff/mm/vmalloc.c 2006-09-04
And still needs fixing in latest mainline 2.4.
> 11:29:33.000000000 -0500
> @@ -298,8 +298,8 @@
> struct vm_struct *area;
> unsigned long size = count << PAGE_SHIFT;
>
> - if (!size || size > (max_mapnr << PAGE_SHIFT))
> - return NULL;
> + if (!count || count > max_mapnr)
> + return NULL;
I'm afraid the tabs got messed up in both the old and new lines.
Also, count is a signed int (whereas size and max_mapnr are both
unsigned longs), so best reject "count <= 0" rather than just "!count".
> area = get_vm_area(size, flags);
> if (!area) {
> return NULL;
Here's a replacement patch for Willy. Anatoli, you didn't sign
off the patch yourself: so I'm assuming Michael is the originator.
From: Michael Chen <micche@ati.com>
(max_mapnr << PAGE_SHIFT) would overflow on a system which has
4GB memory or more, and so could cause vmap to fail every time.
Signed-off-by: Michael Chen <micche@ati.com>
Signed-off-by: Hugh Dickins <hugh@veritas.com>
---
mm/vmalloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- 2.4.34-pre3/mm/vmalloc.c 2004-04-14 14:05:41.000000000 +0100
+++ linux/mm/vmalloc.c 2006-09-23 17:52:59.000000000 +0100
@@ -293,7 +293,7 @@ void * vmap(struct page **pages, int cou
struct vm_struct *area;
unsigned long size = count << PAGE_SHIFT;
- if (!size || size > (max_mapnr << PAGE_SHIFT))
+ if (count <= 0 || count > max_mapnr)
return NULL;
area = get_vm_area(size, flags);
if (!area) {
next prev parent reply other threads:[~2006-09-23 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 15:34 Anatoli Antonovitch
2006-09-23 17:26 ` Hugh Dickins [this message]
2006-09-23 23:55 ` Willy Tarreau
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=Pine.LNX.4.64.0609231759590.30885@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=antonovi@ati.com \
--cc=linux-kernel@vger.kernel.org \
--cc=micche@ati.com \
--cc=tigran@veritas.com \
--cc=w@1wt.eu \
/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®