From: Dave Chinner <david@fromorbit.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: hch@infradead.org, viro@zeniv.linux.org.uk, adilger@sun.com,
corbet@lwn.net, serue@us.ibm.com, neilb@suse.de,
hooanon05@yahoo.co.jp, bfields@fieldses.org,
linux-fsdevel@vger.kernel.org, sfrench@us.ibm.com,
philippe.deniel@CEA.FR, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -V13 0/11] Generic name to handle and open by handle syscalls
Date: Fri, 4 Jun 2010 15:43:28 +1000 [thread overview]
Message-ID: <20100604054328.GA20641@dastard> (raw)
In-Reply-To: <1275581657-7232-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Thu, Jun 03, 2010 at 09:44:06PM +0530, Aneesh Kumar K.V wrote:
> Hi,
>
> The below set of patches implement open by handle support using exportfs
> operations. This allows user space application to map a file name to file
> handle and later open the file using handle. This should be usable
> for userspace NFS [1] and 9P server [2]. XFS already support this with the ioctls
> XFS_IOC_PATH_TO_HANDLE and XFS_IOC_OPEN_BY_HANDLE.
.....
> Example program: (x86_32). (x86_64 would need a different syscall number)
[snip test program]
Just a thought - can you write a set of tests using this (or
similar) test program and integrate them into xfstests?
That will help ensure correctness when implementing the API in other
filesystems (e.g. XFS ;), as well as provide some level of assurance
that we'll notice when we break the code...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2010-06-04 5:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 16:14 [PATCH -V13 0/11] Generic name to handle and open by handle syscalls Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 01/11] exportfs: Return the minimum required handle size Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 02/11] vfs: Add name to file handle conversion support Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 03/11] vfs: Add open by file handle support Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 04/11] vfs: Allow handle based open on symlinks Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 05/11] vfs: Support null pathname in readlink Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 06/11] ext4: Copy fs UUID to superblock Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 07/11] x86: Add new syscalls for x86_32 Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 08/11] x86: Add new syscalls for x86_64 Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 09/11] ext3: Copy fs UUID to superblock Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 10/11] vfs: Support null pathname in faccessat Aneesh Kumar K.V
2010-06-03 16:14 ` [PATCH -V13 11/11] vfs: Support null pathname in linkat Aneesh Kumar K.V
2010-06-04 5:43 ` Dave Chinner [this message]
2010-06-04 6:08 ` [PATCH -V13 0/11] Generic name to handle and open by handle syscalls Aneesh Kumar K. V
2010-06-08 14:18 ` Aneesh Kumar K. V
-- strict thread matches above, loose matches on Subject: below --
2010-06-03 16:08 Aneesh Kumar K.V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100604054328.GA20641@dastard \
--to=david@fromorbit.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bfields@fieldses.org \
--cc=corbet@lwn.net \
--cc=hch@infradead.org \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=philippe.deniel@CEA.FR \
--cc=serue@us.ibm.com \
--cc=sfrench@us.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.