linux-kernel - Re: ping: re: [PATCH 1/1] kernel code that do not handle NULL return of kmem_cache

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: <65B0AD57-F44C-4360-916C-16D26884B09C@suse.de>
Date:	Mon, 2 Dec 2013 10:54:51 +0100
From:	Alexander Graf <agraf@...e.de>
To:	Zhouyi Zhou <yizhouzhou@....ac.cn>
Cc:	Zhouyi Zhou <zhouzhouyi@...il.com>,
	"linux-kernel@...r.kernel.org list" <linux-kernel@...r.kernel.org>,
	linuxppc-dev@...ts.ozlabs.org, kvm-ppc@...r.kernel.org,
	"kvm@...r.kernel.org mailing list" <kvm@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Joerg Roedel <joro@...tes.org>,
	Ben Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: ping: re: [PATCH 1/1] kernel code that do not handle NULL return of kmem_cache_zalloc


On 02.12.2013, at 04:07, Zhouyi Zhou <yizhouzhou@....ac.cn> wrote:

> ping
>>  I do a grep for kmem_cache_zalloc and kmem_cache_alloc
>>  in kernel tree, and find some code do not handle NULL
>>  return of kmem_cache_zalloc correctly
>>  
>>  
>>  Signed-off-by: Zhouyi Zhou <yizhouzhou@....ac.cn>

Thanks a lot for the patch. I'd assume we want something slightly more clever even, similar to Paul's d78bca729.

Please beware that it's usually not a good idea to post patches that span multiple subtrees. I don't want to apply a patch to my kvm tree that touches jffs2 for example, as that's out of my scope. It usually makes a maintainer's life easier if you split up a patch like this according to tree responsibilities.


Alex

--
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/