linux-kernel - RE: [HPDD-discuss] [PATCH 2/11] Staging: lustre: fld: Use kzalloc and kfree

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]

Date:	Fri, 1 May 2015 22:57:45 +0000
From:	"Simmons, James A." <simmonsja@...l.gov>
To:	'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>
CC:	'Julia Lawall' <julia.lawall@...6.fr>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Oleg Drokin <oleg.drokin@...el.com>,
	"HPDD-discuss@...ts.01.org" <HPDD-discuss@...1.01.org>
Subject: RE: [HPDD-discuss] [PATCH 2/11] Staging: lustre: fld: Use kzalloc and
 kfree

>> Yes the LARGE functions do the switching. I was expecting also patches to remove the 
>> OBD_ALLOC_LARGE functions as well which is not the case here.  I do have one question still. The
>> macro __OBD_MALLOC_VERBOSE allowed the ability to simulate memory allocation failures at
>> a certain percentage rate. Does something exist in the kernel to duplicate that functionality?
>
>Yes, no need for lustre to duplicate yet-another-thing the kernel
>already provides :)

The reason for this is that libcfs was written 10+ years ago which was before linux had such nice
features. At that time it was needed to fill the gaps missing which is no longer the case. Libcfs is
really showing its age :-)
--
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/