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
| ||
|
Date: Sat, 6 Jan 2007 12:16:11 -0800 From: Andrew Morton <akpm@...l.org> To: Alexey Dobriyan <adobriyan@...il.com> Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, Neil Brown <neilb@...e.de> Subject: Re: [PATCH] ext2: conditional removal of NFSD code On Sat, 6 Jan 2007 22:58:31 +0300 Alexey Dobriyan <adobriyan@...il.com> wrote: > --- 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. - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists