Thread (7 messages) 7 messages, 4 authors, 2007-01-06

Re: [PATCH] ext2: conditional removal of NFSD code

From: Andrew Morton <hidden>
Date: 2007-01-06 20:16:17
Also in: linux-fsdevel

On Sat, 6 Jan 2007 22:58:31 +0300
Alexey Dobriyan [off-list ref] wrote:
quoted hunk ↗ jump to hunk
--- a/fs/ext2/namei.c
+++ b/fs/ext2/namei.c
@@ -70,6 +70,7 @@ static struct dentry *ext2_lookup(struct
 	return d_splice_alias(inode, dentry);
 }
 
+#if defined(CONFIG_EXPORTFS) || defined(CONFIG_EXPORTFS_MODULE)
 struct dentry *ext2_get_parent(struct dentry *child)
hm.  Officially, one module isn't supposed to know about the presence of
another one at compile-time.  Someone might want to come along and later
configure and compile the nfsd module and then try to load it into a kernel
which wasn't compiled with nfsd enabled.

But given that both modules are in mainline I suspect that nobody would
really be doing that in practice, and in the case of nfsd it might not even
work.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help