[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170814111430.lskrrg3fygpnyx6v@armageddon.cambridge.arm.com>
Date: Mon, 14 Aug 2017 12:14:32 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 1/2] kmemleak: Delete an error message for a failed
memory allocation in two functions
On Mon, Aug 14, 2017 at 11:35:02AM +0200, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@...rs.sourceforge.net>
> Date: Mon, 14 Aug 2017 10:50:22 +0200
>
> Omit an extra message for a memory allocation failure in these functions.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@...rs.sourceforge.net>
> ---
> mm/kmemleak.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
> index 7780cd83a495..c6c798d90b2e 100644
> --- a/mm/kmemleak.c
> +++ b/mm/kmemleak.c
> @@ -555,7 +555,6 @@ static struct kmemleak_object *create_object(unsigned long ptr, size_t size,
>
> object = kmem_cache_alloc(object_cache, gfp_kmemleak_mask(gfp));
> if (!object) {
> - pr_warn("Cannot allocate a kmemleak_object structure\n");
> kmemleak_disable();
I don't really get what this patch is trying to achieve. Given that
kmemleak will be disabled after this, I'd rather know why it happened.
--
Catalin
Powered by blists - more mailing lists