linux-kernel - Re: + fs-cache-generic-filesystem-caching-facility.patch added to -mm tree

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

Date:	Tue, 08 Aug 2006 10:04:56 -0700
From:	Dave Hansen <haveblue@...ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mm-commits@...r.kernel.org, dhowells@...hat.com,
	trond.myklebust@....uio.no, zippel@...ux-m68k.org
Subject: Re: + fs-cache-generic-filesystem-caching-facility.patch added to
	-mm tree

On Fri, 2006-08-04 at 17:09 -0700, akpm@...l.org wrote:
> The attached patch adds a generic intermediary (FS-Cache) by which filesystems
> may call on local caching capabilities, and by which local caching backends may
> make caches available:

I'm getting the following in 2.6.18-rc3-mm2 when I complile AFS  and NFS
into the kernel.  I left FSCACHE as a module somehow, enabled AFS/NFS
caching, and hilarity ensues:

fs/built-in.o(.text+0xbbcd7): In function `nfs_fscache_release_page':
lxc/include/linux/fscache.h:482: undefined reference to
`__fscache_uncache_page'

Is there some way that we can tell fscache's Kconfig option that it can
not be a module if any of the filesystems using it *are*?  Should we
take away the option for fscache to be a module?

-- Dave

-
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/