linux-kernel - Re: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <84144f020607201049g1391d3f4qfdb6f4a0821a5be8@mail.gmail.com>
Date:	Thu, 20 Jul 2006 20:49:08 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Panagiotis Issaris" <takis@....org>
Cc:	"Daniel K." <daniel@...ded.net>,
	"Panagiotis Issaris" <takis@...umba.uhasselt.be>,
	linux-kernel@...r.kernel.org, len.brown@...el.com,
	chas@....nrl.navy.mil, miquel@...uba.ar, kkeil@...e.de,
	benh@...nel.crashing.org, video4linux-list@...hat.com,
	rmk+mmc@....linux.org.uk, Neela.Kolli@...enio.com,
	jgarzik@...ox.com, vandrove@...cvut.cz, adaplas@....net,
	thomas@...ischhofer.net, weissg@...nna.at, philb@....org,
	linux-pcmcia@...ts.infradead.org, jkmaline@...hut.fi,
	paulus@...ba.org
Subject: Re: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.

On 7/20/06, Panagiotis Issaris <takis@....org> wrote:
> I figured someone might want to add extra code in f.e. RIOGetCmddBlk to
> be able to debug/modify memory allocation behavior for the RIO driver
> only. It does look a bit messy though. So I've updated it in my updated
> patch.

Yes, we have people adding those and I keep trying to get rid of them
;-). With Al Viro's slab memory leak tracking patches in-tree and
Catalin's kmemleak on the way, there really is no excuse adding new
ones.
-
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/