From: Ralf Baechle <ralf@linux-mips.org>
To: "tiejun.chen" <tiejun.chen@windriver.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MT-VPE : Fix the usage of kmalloc
Date: Thu, 13 Mar 2008 15:15:13 +0000 [thread overview]
Message-ID: <20080313151513.GA4368@linux-mips.org> (raw)
In-Reply-To: <47D8BDDC.9010607@windriver.com>
On Thu, Mar 13, 2008 at 01:38:36PM +0800, tiejun.chen wrote:
> The return value of kmalloc() should be check, otherwise it is potential
> risk.
>
> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
> ---
> vpe.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
>
> diff --git a/arch/mips/kernel/vpe.c b/arch/mips/kernel/vpe.c
> index c06eb81..35767de 100644
> --- a/arch/mips/kernel/vpe.c
> +++ b/arch/mips/kernel/vpe.c
> @@ -885,6 +885,10 @@ static int vpe_elfload(struct vpe * v)
> }
>
> v->load_addr = alloc_progmem(mod.core_size);
> +#ifndef CONFIG_MIPS_VPE_LOADER_TOM
> + if (!(v->load_addr))
> + return -ENOMEM;
> +#endif
Your mailer converted the tabs into whitespace so the patch doesn't apply.
Anyway, I fixed things in a slightly different way which hopefully
avoids throwing in more #ifdefs and will safe a little code for the
!CONFIG_MIPS_VPE_LOADER_TOM case.
Thanks,
Ralf
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
diff --git a/arch/mips/kernel/vpe.c b/arch/mips/kernel/vpe.c
index eed2dc4..39804c5 100644
--- a/arch/mips/kernel/vpe.c
+++ b/arch/mips/kernel/vpe.c
@@ -262,13 +262,21 @@ void dump_mtregs(void)
/* Find some VPE program space */
static void *alloc_progmem(unsigned long len)
{
+ void *addr;
+
#ifdef CONFIG_MIPS_VPE_LOADER_TOM
- /* this means you must tell linux to use less memory than you physically have */
- return pfn_to_kaddr(max_pfn);
+ /*
+ * This means you must tell Linux to use less memory than you
+ * physically have, for example by passing a mem= boot argument.
+ */
+ addr = pfn_to_kaddr(max_pfn);
+ memset(addr, 0, len);
#else
- // simple grab some mem for now
- return kmalloc(len, GFP_KERNEL);
+ /* simple grab some mem for now */
+ addr = kzalloc(len, GFP_KERNEL);
#endif
+
+ return addr;
}
static void release_progmem(void *ptr)
@@ -884,9 +892,10 @@ static int vpe_elfload(struct vpe * v)
}
v->load_addr = alloc_progmem(mod.core_size);
- memset(v->load_addr, 0, mod.core_size);
+ if (!v->load_addr)
+ return -ENOMEM;
- printk("VPE loader: loading to %p\n", v->load_addr);
+ pr_info("VPE loader: loading to %p\n", v->load_addr);
if (relocate) {
for (i = 0; i < hdr->e_shnum; i++) {
prev parent reply other threads:[~2008-03-13 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 5:38 [PATCH] MT-VPE : Fix the usage of kmalloc tiejun.chen
2008-03-13 15:15 ` Ralf Baechle [this message]
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=20080313151513.GA4368@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=tiejun.chen@windriver.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