From: Josef Bacik <jbacik@fusionio.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Josef Bacik <jbacik@fusionio.com>, <xfs@oss.sgi.com>,
<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] xfstests: add generic/321 to test fsync() on directories V2
Date: Mon, 25 Nov 2013 16:37:51 -0500 [thread overview]
Message-ID: <20131125213751.GA3949@localhost.localdomain> (raw)
In-Reply-To: <20131125161216.GA5085@infradead.org>
On Mon, Nov 25, 2013 at 08:12:16AM -0800, Christoph Hellwig wrote:
> On Fri, Nov 15, 2013 at 01:01:03PM -0500, Josef Bacik wrote:
> > Btrfs had some issues with fsync()'ing directories and fsync()'ing after
> > renames. These three new tests cover the 3 different issues we were seeing.
> > This breaks out the dmflakey stuff into a common helper to be shared between
> > generic/311 and generic/321. Thanks,
> >
> > Signed-off-by: Josef Bacik <jbacik@fusionio.com>
>
> This doesn't seem to actually create the common/dmflakey file.
Eek sorry about that, I'll resend.
Josef
next prev parent reply other threads:[~2013-11-25 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 18:01 [PATCH 1/2] xfstests: add generic/321 to test fsync() on directories V2 Josef Bacik
2013-11-15 18:01 ` [PATCH 2/2] xfstests: add a rename fsync test Josef Bacik
2013-11-18 13:46 ` Christoph Hellwig
2013-11-25 16:12 ` [PATCH 1/2] xfstests: add generic/321 to test fsync() on directories V2 Christoph Hellwig
2013-11-25 21:37 ` Josef Bacik [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-25 21:40 Josef Bacik
2013-11-26 14:30 ` Christoph Hellwig
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=20131125213751.GA3949@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.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).