From: Eryu Guan <guaneryu@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests <fstests@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: Re: [PATCH] generic/223: port t_stripealign to FIEMAP
Date: Sun, 17 Jun 2018 22:39:00 +0800 [thread overview]
Message-ID: <20180617143900.GH2780@desktop> (raw)
In-Reply-To: <20180615024901.GF2780@desktop>
On Fri, Jun 15, 2018 at 10:49:01AM +0800, Eryu Guan wrote:
> On Wed, Jun 13, 2018 at 03:50:57PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Since XFS has deprecated FIBMAP on FSDAX filesystems, we can't use
> > FIBMAP to verify stripe alignment anymore. FIEMAP has existed for quite
> > some time now, so port it to use that instead, and only fall back to
> > FIBMAP if FIEMAP doesn't exist.
> >
> > Tested-by: ross.zwisler@linux.intel.com
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > src/t_stripealign.c | 72 +++++++++++++++++++++++++++++++++++++++++++--------
> > 1 file changed, 61 insertions(+), 11 deletions(-)
> >
> > diff --git a/src/t_stripealign.c b/src/t_stripealign.c
> > index 05ed36b5..690f743a 100644
> > --- a/src/t_stripealign.c
> > +++ b/src/t_stripealign.c
> > @@ -17,8 +17,13 @@
> > #include <fcntl.h>
> > #include <stdio.h>
> > #include <sys/ioctl.h>
> > +#include <linux/fiemap.h>
> > +#include <linux/fs.h>
>
> As it requires <linux/fiemap.h> now, looks like we should update
> src/Makefile too to only compile it when "HAVE_FIEMAP" is true.
>
> ifeq ($(HAVE_FIEMAP), true)
> LINUX_TARGETS += fiemap-tester t_stripealign
> endif
JFYI, I fixed it on commit (also remove t_stripealign from TARGETS).
Thanks,
Eryu
prev parent reply other threads:[~2018-06-17 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 22:50 [PATCH] generic/223: port t_stripealign to FIEMAP Darrick J. Wong
2018-06-15 2:49 ` Eryu Guan
2018-06-17 14:39 ` Eryu Guan [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=20180617143900.GH2780@desktop \
--to=guaneryu@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ross.zwisler@linux.intel.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).