From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Is jdm_delete_filehandle part of a public API?
Date: Mon, 4 Aug 2014 12:20:05 +1000 [thread overview]
Message-ID: <20140804022005.GV20518@dastard> (raw)
In-Reply-To: <20140801135305.GA31894@infradead.org>
On Fri, Aug 01, 2014 at 06:53:05AM -0700, Christoph Hellwig wrote:
> Talking about libhandle: this one has been a bit bitrotted. Maybe it's
> a good time to move everything over to the kernel by handle syscalls
> and deprecated it?
First you need to make the kernel by-handle interfaces handle the
sae functionality as the XFS by-handle ioctls.
1. O_NOCMTIME doesn't exist, and so there's no way to do
invisible IO on files.
2. Can we construct VFs filehandles in userspace from
bulkstat information (dump, xfs_fsr and others rely on
this capability)?
3. The kernel by-handle interfaces cannot manipulate
attributes at all (i.e. attr-list, attr-multi
functionality).
So until the VFS by-handle interfaces can do these things, we can't
change libhandle over to use the newer kernel interfaces.
I'm also pretty sure the incompatible handle format would mean
big problems if someone were to be storing file handles in userspace
and they upgrade their version of libhandle. i.e. such a library
implementation change is not forwards or backwards compatible with
existing applications, but bumping the major shared library version
should solve that problem.
However, these are all solvable problems. It's definitely a low
priority for me to do this, but if you want to do it patches will
definitely be accepted ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-08-04 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 17:31 Is jdm_delete_filehandle part of a public API? Eric Sandeen
2014-07-29 18:18 ` Mark Tinguely
2014-07-29 20:04 ` Mark Tinguely
2014-07-29 20:18 ` Eric Sandeen
2014-07-29 20:54 ` Mark Tinguely
2014-07-29 23:46 ` Dave Chinner
2014-08-01 13:53 ` Christoph Hellwig
2014-08-04 2:20 ` Dave Chinner [this message]
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=20140804022005.GV20518@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox