From: Eryu Guan <eguan@redhat.com>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] fstests: generic test for fsync after adding a link and moving other inode
Date: Thu, 7 Apr 2016 15:36:43 +0800 [thread overview]
Message-ID: <20160407073643.GP10345@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1459980716-4705-1-git-send-email-fdmanana@kernel.org>
On Wed, Apr 06, 2016 at 11:11:56PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Test that if we create a hard link for a file F in some directory A,
> then move some directory or file B from its parent directory C into
> directory A, fsync file F, power fail and mount the filesystem, the
> directory/file B is located only at directory A and both links for
> file F exist.
>
> This test is motivated by an issue found in btrfs which is fixed by the
> following patch for the linux kernel:
>
> Btrfs: fix for incorrect directory entries after fsync log replay
>
> Tested against ext3/4, xfs, reiserfs and f2fs.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Looks good to me. Test passed with ext3/4 and xfs, failed with btrfs as
expected.
Reviewed-by: Eryu Guan <eguan@redhat.com>
prev parent reply other threads:[~2016-04-07 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 22:11 [PATCH] fstests: generic test for fsync after adding a link and moving other inode fdmanana
2016-04-07 7:36 ` 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=20160407073643.GP10345@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).