[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20160804085055.GB2509@localhost>
Date: Thu, 4 Aug 2016 14:50:55 +0600
From: Alexnader Kuleshov <kuleshovmail@...il.com>
To: Nicholas Krause <xerofoify@...il.com>
Cc: viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
msalter@...hat.com, kuleshovmail@...il.com,
david.vrabel@...rix.com, vbabka@...e.cz, ard.biesheuvel@...aro.org,
jgross@...e.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] fs:Fix kmemleak leak warning in getname_flags about
working on unitialized memory
On 08-03-16, Nicholas Krause wrote:
> This fixes a kmemleak leak warning complaining about working on
> unitializied memory as found in the function, getname_flages. Seems
s/getname_flages/getname_flags
> that we are indeed working on unitialized memory, as the filename
> char pointer is never made to point to the filname structure's result
> member for holding it's name, fix this by using memcpy to copy the
> filname structure pointer's, name to the char pointer passed to this
> function.
>
> Signed-off-by: Nicholas Krause <xerofoify@...il.com>
> ---
> fs/namei.c | 1 +
> mm/early_ioremap.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/fs/namei.c b/fs/namei.c
> index c386a32..6b18d57 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -196,6 +196,7 @@ getname_flags(const char __user *filename, int flags, int *empty)
> }
> }
>
> + memcpy((char *)result->name, filename, len);
> result->uptr = filename;
> result->aname = NULL;
> audit_getname(result);
> diff --git a/mm/early_ioremap.c b/mm/early_ioremap.c
> index 6d5717b..92c5235 100644
> --- a/mm/early_ioremap.c
> +++ b/mm/early_ioremap.c
> @@ -215,6 +215,7 @@ early_ioremap(resource_size_t phys_addr, unsigned long size)
> void __init *
> early_memremap(resource_size_t phys_addr, unsigned long size)
> {
> + dump_stack();
Why?
> return (__force void *)__early_ioremap(phys_addr, size,
> FIXMAP_PAGE_NORMAL);
> }
> --
> 2.7.4
>
Powered by blists - more mailing lists