From: Josef Bacik <jbacik@fb.com>
To: Fengguang Wu <fengguang.wu@intel.com>,
Steven Whitehouse <swhiteho@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
<linux-fsdevel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [btrfs/i_size] xfstests generic/299 TFAIL
Date: Thu, 30 Jan 2014 16:52:25 -0500 [thread overview]
Message-ID: <52EAC999.7070609@fb.com> (raw)
In-Reply-To: <20140130035440.GB12017@localhost>
On 01/29/2014 10:54 PM, Fengguang Wu wrote:
> Hi Steven,
>
> We noticed xfstests generic/299 TFAIL on btrfs since
>
> commit 9fe55eea7e4b444bafc42fa0000cc2d1d2847275
> Author: Steven Whitehouse <swhiteho@redhat.com>
> AuthorDate: Fri Jan 24 14:42:22 2014 +0000
> Commit: Al Viro <viro@zeniv.linux.org.uk>
> CommitDate: Sun Jan 26 08:26:42 2014 -0500
>
> Fix race when checking i_size on direct i/o read
>
Ok this took a bit but it's because truncate() can fail on btrfs and the
test didn't take this into account. I'll send a patch for the test.
Thanks,
Josef
prev parent reply other threads:[~2014-01-30 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 3:54 [btrfs/i_size] xfstests generic/299 TFAIL Fengguang Wu
2014-01-30 21:52 ` Josef Bacik [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=52EAC999.7070609@fb.com \
--to=jbacik@fb.com \
--cc=fengguang.wu@intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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).