All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>, fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] generic: test FIEMAP on extended attribute blocks
Date: Fri, 7 Apr 2017 17:26:16 +0800	[thread overview]
Message-ID: <20170407092616.GT22845@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170406160130.GX4864@birch.djwong.org>

On Thu, Apr 06, 2017 at 09:01:30AM -0700, Darrick J. Wong wrote:
> Make sure that FIEMAP produces some output when we add enough xattrs
> to force the xattrs to be stored in an external block.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>

Test itself looks fine to me. But given that there's disagreement on
fiemap on xattr (still an reasonable test?) and test crashes debug built
& 512b block size XFS, I'll hold this test for now.

Thanks,
Eryu

  reply	other threads:[~2017-04-07  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 16:01 [PATCH] generic: test FIEMAP on extended attribute blocks Darrick J. Wong
2017-04-07  9:26 ` Eryu Guan [this message]
2017-04-07 15:46   ` 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=20170407092616.GT22845@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.