linux-kernel - Re: [PATCH] kmemleak: Show where early

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1313155037.18583.321.camel@gandalf.stny.rr.com>
Date:	Fri, 12 Aug 2011 09:17:17 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] kmemleak: Show where early_log issues come from

On Fri, 2011-08-12 at 10:40 +0100, Catalin Marinas wrote:

> Thanks for the patch, it makes sense. I was wondering whether we should
> extend the above to the other early kmemleak API calls (apart from
> KMEMLEAK_ALLOC). Also, to avoid some code duplication, maybe something
> like below:
> 

Makes sense to me.

Acked-by: Steven Rostedt <rostedt@...dmis.org>

-- Steve

> +
> +		if (ret < 0)
> +			print_log_stack(log);
>  	}
>  }
>  
> 
> Thanks.
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/