linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] add a FMODE flag to make XFS invisible I/O less hacky
Date: Tue, 2 Dec 2008 11:19:54 +0100	[thread overview]
Message-ID: <20081202101954.GA17757@lst.de> (raw)
In-Reply-To: <20081130091603.GA3315@lst.de>

On Sun, Nov 30, 2008 at 10:16:04AM +0100, Christoph Hellwig wrote:
> On Fri, Nov 28, 2008 at 11:30:52AM +0000, Al Viro wrote:
> > On Fri, Nov 28, 2008 at 12:24:02PM +0100, Christoph Hellwig wrote:
> > > XFS has a mode called invisble I/O that doesn't update any of the
> > > timestamps.  It's used for HSM-style applications and exposed through
> > > the nasty open by handle ioctl.
> > > 
> > > Instead of doing directly assignment of file operations that set an
> > > internal flag for it add a new FMODE_INVISIBLE flag that we can check
> > > in the normal file operations.
> > 
> > Seeing that it's similar to O_NOATIME, why not do it in O_... space?
> 
> For now I just want to get rid of the horrible hack in XFS.  Adding this
> as a user-visible feature might be a good idea that those who need it
> can submit.

Taking about that submission, any chance I could just put in this with a
flag allocated high enough to not clash in the XFS tree and then sort
out things once the vfs and xfs trees get merged for 2.6.29?  That's
help making progress on the XFS side a lot, as there would be tons of
merge conflicts there othwerwise.  (compat_ioctl handling just got a big
rework, touch just 2/3s of the hunks of this patch)

  reply	other threads:[~2008-12-02 10:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 11:24 [PATCH] add a FMODE flag to make XFS invisible I/O less hacky Christoph Hellwig
2008-11-28 11:30 ` Al Viro
2008-11-30  9:16   ` Christoph Hellwig
2008-12-02 10:19     ` Christoph Hellwig [this message]
2008-11-28 22:58 ` Andreas Dilger
2008-11-30  9:18   ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2008-12-03 17:45 Christoph Hellwig

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=20081202101954.GA17757@lst.de \
    --to=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).