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]

Message-ID: <CDD0100C-8761-4979-9B9A-2D52713C9A1E@intel.com>
Date:	Sun, 3 May 2015 03:12:31 +0000
From:	"Drokin, Oleg" <oleg.drokin@...el.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"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>,
	Julia Lawall <Julia.Lawall@...6.fr>,
	"HPDD-discuss@...ts.01.org" <HPDD-discuss@...1.01.org>,
	"Simmons, James A." <simmonsja@...l.gov>
Subject: Re: [HPDD-discuss] [PATCH 2/11] Staging: lustre: fld: Use kzalloc
 and kfree

Hello!

On May 2, 2015, at 4:14 AM, Dan Carpenter wrote:

> On Fri, May 01, 2015 at 09:13:11PM +0000, Drokin, Oleg wrote:
>>>> The patch was submitted.
>>>> But it depends on a symbol that's not exported.
>>>> I was not able to change that.
>>>> http://www.spinics.net/lists/linux-mm/msg83997.html
>>> 
>>> But you were given a hint on how to change that :)
>> 
>> Well, the hint amounted to "don't do vmalloc if you cannot live with the
>> GFP_KERNEL" allocations.
>> 
> 
> Which email is that?

Ah, my memory is playing tricks, it appears.
There was just a pointer to the "other discussions" where this advice was given it appears.

> I only see where David says to implement vmalloc_node_gfp() and the talk
> was about if that makes sense from a style perspective and then dies.
> 
> Anyway, this only seems to affect ptlrpc_alloc_rqbd() since  I think
> that's the only place which calls OBD_CPT_ALLOC_PTR().  The rest can use
> __vmalloc().

I guess so.

Bye,
   Oleg--
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/