mirror of
https://github.com/team-infusion-developers/android_kernel_samsung_msm8976.git
synced 2024-10-31 18:09:19 +00:00
75f96ce6e7
Fix build errors by correcting DLM dependencies in GFS2. Build errors happen when CONFIG_GFS2_FS_LOCKING_DLM=y and CONFIG_DLM=m: fs/built-in.o: In function `gfs2_lock': file.c:(.text+0xc7abd): undefined reference to `dlm_posix_get' file.c:(.text+0xc7ad0): undefined reference to `dlm_posix_unlock' file.c:(.text+0xc7ad9): undefined reference to `dlm_posix_lock' fs/built-in.o: In function `gdlm_unmount': lock_dlm.c:(.text+0xd6e5b): undefined reference to `dlm_release_lockspace' fs/built-in.o: In function `sync_unlock': lock_dlm.c:(.text+0xd6e9e): undefined reference to `dlm_unlock' fs/built-in.o: In function `sync_lock': lock_dlm.c:(.text+0xd6fb6): undefined reference to `dlm_lock' fs/built-in.o: In function `gdlm_put_lock': lock_dlm.c:(.text+0xd7238): undefined reference to `dlm_unlock' fs/built-in.o: In function `gdlm_mount': lock_dlm.c:(.text+0xd753e): undefined reference to `dlm_new_lockspace' lock_dlm.c:(.text+0xd79d3): undefined reference to `dlm_release_lockspace' fs/built-in.o: In function `gdlm_lock': lock_dlm.c:(.text+0xd8179): undefined reference to `dlm_lock' fs/built-in.o: In function `gdlm_cancel': lock_dlm.c:(.text+0xd6b22): undefined reference to `dlm_unlock' Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
35 lines
1.4 KiB
Text
35 lines
1.4 KiB
Text
config GFS2_FS
|
|
tristate "GFS2 file system support"
|
|
depends on (64BIT || LBDAF)
|
|
select FS_POSIX_ACL
|
|
select CRC32
|
|
select QUOTACTL
|
|
help
|
|
A cluster filesystem.
|
|
|
|
Allows a cluster of computers to simultaneously use a block device
|
|
that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads
|
|
and writes to the block device like a local filesystem, but also uses
|
|
a lock module to allow the computers coordinate their I/O so
|
|
filesystem consistency is maintained. One of the nifty features of
|
|
GFS is perfect consistency -- changes made to the filesystem on one
|
|
machine show up immediately on all other machines in the cluster.
|
|
|
|
To use the GFS2 filesystem in a cluster, you will need to enable
|
|
the locking module below. Documentation and utilities for GFS2 can
|
|
be found here: http://sources.redhat.com/cluster
|
|
|
|
The "nolock" lock module is now built in to GFS2 by default. If
|
|
you want to use the DLM, be sure to enable HOTPLUG and IPv4/6
|
|
networking.
|
|
|
|
config GFS2_FS_LOCKING_DLM
|
|
bool "GFS2 DLM locking"
|
|
depends on (GFS2_FS!=n) && NET && INET && (IPV6 || IPV6=n) && \
|
|
HOTPLUG && CONFIGFS_FS && SYSFS && (DLM=y || DLM=GFS2_FS)
|
|
help
|
|
Multiple node locking module for GFS2
|
|
|
|
Most users of GFS2 will require this. It provides the locking
|
|
interface between GFS2 and the DLM, which is required to use GFS2
|
|
in a cluster environment.
|