From: "Guillermo Julián Moreno" <guillermo.julian@naudit.es>
To: linux-mm@kvack.org
Subject: Re: [PATCH] mm: fix overflow in vm_map_ram
Date: Thu, 26 May 2016 09:38:04 +0200 [thread overview]
Message-ID: <etPan.5746a7e1.1cc53686.1602@naudit.es> (raw)
In-Reply-To: <etPan.57175fb3.7a271c6b.2bd@naudit.es>
On 20 April 2016 at 12:53:41, Guillermo Julián Moreno (guillermo.julian@naudit.es(mailto:guillermo.julian@naudit.es)) wrote:
>
> When remapping pages accounting for 4G or more memory space, the
> operation 'count << PAGE_SHIFT' overflows as it is performed on an
> integer. Solution: cast before doing the bitshift.
>
> Signed-off-by: Guillermo Julián
> ---
> mm/vmalloc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index ae7d20b..97257e4 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -1114,7 +1114,7 @@ EXPORT_SYMBOL(vm_unmap_ram);
> */
> void *vm_map_ram(struct page **pages, unsigned int count, int node, pgprot_t prot)
> {
> - unsigned long size = count << PAGE_SHIFT;
> + unsigned long size = ((unsigned long) count) << PAGE_SHIFT;
> unsigned long addr;
> void *mem;
>
> @@ -1484,7 +1484,7 @@ static void __vunmap(const void *addr, int deallocate_pages)
> kfree(area);
> return;
> }
> -
> +
> /**
> * vfree - release memory allocated by vmalloc()
> * @addr: memory base address
> --
> 1.8.3.1
Hello, has anyone taken a look at this patch?
Guillermo Julián
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-05-26 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 10:53 [PATCH] mm: fix overflow in vm_map_ram Guillermo Julián Moreno
2016-05-26 7:38 ` Guillermo Julián Moreno [this message]
2016-05-26 21:28 ` Andrew Morton
2016-05-27 8:25 ` guillermo.julian
2016-05-27 20:20 ` Andrew Morton
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=etPan.5746a7e1.1cc53686.1602@naudit.es \
--to=guillermo.julian@naudit.es \
--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;
as well as URLs for NNTP newsgroup(s).