linux-kernel - Re: NFS and partitioned md

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

Date:	Thu, 20 Jul 2006 11:07:36 +0200
From:	Frank van Maarseveen <frankvm@...nkvm.com>
To:	Neil Brown <neilb@...e.de>
Cc:	Martin Filip <bugtraq@...ula.net>,
	David Greaves <david@...eaves.com>,
	linux-kernel@...r.kernel.org,
	Linux NFS mailing list <nfs@...ts.sourceforge.net>
Subject: Re: NFS and partitioned md

On Thu, Jul 20, 2006 at 10:30:01AM +1000, Neil Brown wrote:
> On Tuesday July 18, bugtraq@...ula.net wrote:
> > Hi,
> > 
> > my solution was to use fsid parameter for exports... maybe some other
> > mechanism for selecting fsids could be created instead of fsid = device
> > minor
> 
> Yes.  Better management of fsid is on my wishlist for nfs-utils.
> Unfortunately I haven't had any really clever ideas yet.

I'd like to "virtualize" exports such that it is possible to transplant
disks/partitions from one machine into another without having to bother
with device numbering. One step in that direction is to derive the fsid
from an IP address. The server machine needs an additional IP address
for every export entry. This IP address is determined by deriving
a hostname from the last pathname component of the export entry and
resolving it. E.g. something like:

/etc/exports:
	/exported/path/name	*(rw,sync,no_root_squash,no_subtree_check,fsid="nfs-%s")

This would set the fsid to the IP address of host "nfs-name".

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