linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
	Dan Williams <dan.j.williams@intel.com>,
	Christoph Hellwig <hch@infradead.org>,
	Xiong Zhou <xzhou@redhat.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>,
	fstests <fstests@vger.kernel.org>,
	linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: ioctl FIBMAP for dax gone in v4.17-rc1
Date: Tue, 17 Apr 2018 19:34:59 -0400	[thread overview]
Message-ID: <20180417233459.GB23194@thunk.org> (raw)
In-Reply-To: <20180417175007.GB5210@magnolia>

On Tue, Apr 17, 2018 at 10:50:07AM -0700, Darrick J. Wong wrote:
> syslinux does FIEMAP w/ FIBMAP fallback.
> 
> lilo & elilo still use FIBMAP only, but lilo hasn't seen a release since
> 2015 and elilo 2013.  I prefer not to add FIBMAP support in XFS-DAX for
> the singular case of booting off pmem via lilo.

It shouldn't be that hard to write a userspace emulation layer which
exports a FIBMAP-like functional interface but gets the information
from the kernel using the FIMAP ioctl....

					- Ted

  reply	other threads:[~2018-04-17 23:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180417144059.nwbbynhgq3k3i63q@XZHOUW.usersys.redhat.com>
2018-04-17 16:10 ` ioctl FIBMAP for dax gone in v4.17-rc1 Christoph Hellwig
2018-04-17 16:53   ` Dan Williams
2018-04-17 16:57     ` Darrick J. Wong
2018-04-17 17:05       ` Dan Williams
2018-04-17 17:40       ` Andreas Dilger
2018-04-17 17:47         ` Dan Williams
2018-04-17 17:50         ` Darrick J. Wong
2018-04-17 23:34           ` Theodore Y. Ts'o [this message]
2018-04-17 23:36           ` Dave Chinner

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=20180417233459.GB23194@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=dan.j.williams@intel.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=xzhou@redhat.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;
as well as URLs for NNTP newsgroup(s).