public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Allison Henderson <allison.henderson@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: [RFCRAP DONOTMERGE PATCH 0/2] xfs: parent pointers
Date: Thu, 7 Dec 2017 19:54:57 -0800	[thread overview]
Message-ID: <20171208035457.GD19219@magnolia> (raw)

Hi all,

So I've been working in my spare time (ha ha) to build a prototype
parent pointer ioctl backend so that I can play around with the
userspace side of things -- namely (cough) having xfs_scrub be able to
resolve an (ino, gen) tuple back to a user-friendly file path.

The first ugly patch attacks the dentry cache to use d_parent to provide
one of the parents of some file.  Obviously, this is totally deficient
as we can only report one parent and the file has to have been opened
via path at some previous point in time, and I bet the locking is
totally wrong.  It's too ugly to live but it /does/ function as a stub.

The second patch implements two iterators atop the parent pointer ioctl
we've been tossing around on the mailing list -- one to return parents
of an open file/file handle, and a second one to return all the paths of
an open file/file handle, and plunges it into (part of) xfs_scrub and
the xfs_io parent command.  Note that I'm expecting xfs_scrub/xfs_repair
to take over parent pointer checking and fixing, so I removed the
checker function from xfs_io.

This is _not_ a substitute for Allison's parent pointer patches, as
they provide the meat of the real feature... but seeing how much
bikeshedding ioctls invite, we might as well start the reconciliation
process now.

--D

             reply	other threads:[~2017-12-08  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  3:54 Darrick J. Wong [this message]
2017-12-08  4:02 ` [RFCRAP DONOTMERGE PATCH 1/2] xfs: sketchy implementation of parent pointers Darrick J. Wong
2017-12-08  7:52   ` Amir Goldstein
2017-12-08  4:03 ` [RFCRAP DONOTMERGE PATCH 2/2] xfsprogs: implement the upper half " Darrick J. Wong

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=20171208035457.GD19219@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=allison.henderson@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    /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