linux-kernel - Re: [PATCH] Allow sharing xvmalloc for zram and zcache

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: <4D5454CC.1000609@vflare.org>
Date:	Fri, 11 Feb 2011 02:42:44 +0530
From:	Nitin Gupta <ngupta@...are.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Dan Magenheimer <dan.magenheimer@...cle.com>,
	linux-next <linux-next@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Allow sharing xvmalloc for zram and zcache

On 02/11/2011 02:38 AM, Randy Dunlap wrote:
> On 02/10/11 13:00, Nitin Gupta wrote:
>> Both zram and zcache use xvmalloc allocator. If xvmalloc
>> is compiled separately for both of them, we will get linker
>> error if they are both selected as "built-in". We can also
>> get linker error regarding missing xvmalloc symbols if zram
>> is not built.
>>
>> So, we now compile xvmalloc separately and export its symbols
>> which are then used by both of zram and zcache.
>>
>> Signed-off-by: Nitin Gupta<ngupta@...are.org>
>
> Acked-by: Randy Dunlap<randy.dunlap@...cle.com>
>
>
> but what does this patch apply to?  It does not apply cleanly to
> linux-next of 20110210.
>

This applies to staging-2.6. I thought linux-next won't be that 
different so as to produce conflicts. Can you please send reject files, 
or let me fetch linux-next tree and will soon post patch against the same.

Thanks,
Nitin
--
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/