| 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: Mon, 27 Aug 2007 20:32:51 +0200 From: Gabriel Barazer <gabriel@...va.fr> To: nfsv4@...ux-nfs.org CC: linux-kernel@...r.kernel.org, nfs@...ts.sourceforge.net, jkar8572@...rs.sourceforge.net Subject: nfs4 filesystem mounted via the "bind" option reports wrong fstype Hi, A nfs4 filesystem, mounted elsewhere via the "bind" option (the usual way to do with nfsv4 and its pseudofs), reports wrong fstype "nfs" instead of "nfs4" filesystem. An example is much easier to understand : Server-side : - /exports is the pseudo root filesystem (fsid=0 option in /etc/exports) - /exports/data is a mountpoint for another filesystem (not the same device-id as /exports). This condition seems to be what triggers the bug - /exports/data must be exported with the "nohide" option (again, the usual way to do se with nfsv4) Client-side : - mount server:/ on /imports - mount "bind" /imports/data on /home/data (this magically shows a second nfs mount in /proc/mounts) And here is the bug : this second mount is of fstype "nfs" instead of "nfs4" although the options field contains "vers=4". This is like a cosmetic bug, but this becomes a problem when some apps need to differentiate nfs and nfs4 fstype (e.g. linuxquota uses it to know how to handle the nfs source-path) Gabriel - 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/
Powered by blists - more mailing lists