[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5DF5C974-092B-4CE6-B11D-2DBB73782149@dilger.ca>
Date: Fri, 9 Jul 2010 12:42:42 -0600
From: Andreas Dilger <adilger@...ger.ca>
To: Neil Brown <neilb@...e.de>
Cc: "Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>,
"J. Bruce Fields" <bfields@...ldses.org>,
Miklos Szeredi <miklos@...redi.hu>,
Dave Chinner <david@...morbit.com>,
Christoph Hellwig <hch@...radead.org>,
"viro@...iv.linux.org.uk Viro" <viro@...iv.linux.org.uk>,
"corbet@....net Corbet" <corbet@....net>,
"hooanon05@...oo.co.jp Okajima" <hooanon05@...oo.co.jp>,
linux-fsdevel@...r.kernel.org,
"sfrench@...ibm.com French" <sfrench@...ibm.com>,
"philippe.deniel@....FR Deniel" <philippe.deniel@....FR>,
"linux-kernel@...r.kernel.org Mailinglist"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -V14 0/11] Generic name to handle and open by handle syscalls
On 2010-07-08, at 06:21, Neil Brown wrote:
> On Thu, 08 Jul 2010 16:10:09 +0530
> "Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com> wrote:
>> How about adding mnt_id to the handle ? Documentation file says it is unique
>>
>> (1) mount ID: unique identifier of the mount (may be reused after umount)
But this value is not persistent across a reboot, or even an umount/mount so it is not useful as an identifier.
I suppose one way to resolve this issue is to just allow the underlying filesystem to supply a completely opaque filehandle to userspace. For local filesystems that don't care about persistence or uniqueness between nodes they can use something like mount_id, and for distributed/clustered filesystems they can include a globally-unique identifier.
Cheers, Andreas
--
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