linux-kernel - RE: linux-next still missing patch for zcache modular Kconfig/build issue

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: <fc9a9123-cc27-4754-9222-796890553ee6@default>
Date:	Wed, 23 Feb 2011 12:23:34 -0800 (PST)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	Valdis.Kletnieks@...edu, Stephen Rothwell <sfr@...b.auug.org.au>,
	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, Nitin Gupta <ngupta@...are.org>
Subject: RE: linux-next still missing patch for zcache modular Kconfig/build
 issue

> From: Valdis.Kletnieks@...edu [mailto:Valdis.Kletnieks@...edu]
> Sent: Wednesday, February 23, 2011 1:09 PM
> Subject: linux-next still missing patch for zcache modular
> Kconfig/build issue
> 
> I know this is a known and solved problem with CONFIG_ZCACHE=m I hit a
> while back:
> 
>   Building modules, stage 2.
>   MODPOST 258 modules
> ERROR: "xv_malloc" [drivers/staging/zcache/zcache.ko] undefined!
> ERROR: "tmem_new_pool" [drivers/staging/zcache/zcache.ko] undefined!
> ERROR: "tmem_put" [drivers/staging/zcache/zcache.ko] undefined!
> ERROR: "tmem_destroy_pool" [drivers/staging/zcache/zcache.ko]
> undefined!
> ERROR: "xv_free" [drivers/staging/zcache/zcache.ko] undefined!
> ERROR: "xv_get_object_size" [drivers/staging/zcache/zcache.ko]
> undefined!
> ERROR: "tmem_get" [drivers/staging/zcache/zcache.ko] undefined!
> ERROR: "tmem_flush_object" [drivers/staging/zcache/zcache.ko]
> undefined!
> ERROR: "tmem_flush_page" [drivers/staging/zcache/zcache.ko] undefined!
> 
> The patch for this isn't in the linux-next tree I pulled yesterday -
> what happened to it?


GregKH hasn't yet pulled the fix into staging-next, which feeds
into linux-next.  See:

https://lkml.org/lkml/2011/2/18/311 
https://lkml.org/lkml/2011/2/18/342 
--
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/