public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] geceric/362: check truncate can update file size correctly when truncate fails
Date: Thu, 30 Jun 2016 21:52:37 +0800	[thread overview]
Message-ID: <20160630135237.GG23649@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160630082549.27201-1-wangxg.fnst@cn.fujitsu.com>

On Thu, Jun 30, 2016 at 04:25:49PM +0800, Wang Xiaoguang wrote:
> In btrfs, when truncate operation fails for enospc reason, file may still
> have some disk blocks, but it will fail to update filesize accordingly.
> 
> Kernel commit c0d2f61 has fixed this bug for btrfs:
>     btrfs: fix disk_i_size update bug when ftruncate() fails
> 
> Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
> ---
> v2: move this test to generic test and add comments why testcase
> use reflink.

Thanks for the updated version. Did it fail for you when testing on
unpatched kernel? I ran the test more than 10 times on 4.6 kernel (which
doesn't have the fix) and all passed, as well as RHEL7 kernel.

Can you please confirm?

Thanks,
Eryu

  reply	other threads:[~2016-06-30 13:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  7:36 [PATCH] btrfs: check truncate can update file size correctly when truncate fails Wang Xiaoguang
2016-06-23  8:27 ` Eryu Guan
2016-06-29  3:22   ` Wang Xiaoguang
2016-06-30  8:25   ` [PATCH v2] geceric/362: " Wang Xiaoguang
2016-06-30 13:52     ` Eryu Guan [this message]
2016-07-01  1:25       ` Wang Xiaoguang
2016-07-01  2:28       ` Wang Xiaoguang
2016-07-01  2:55         ` Eryu Guan
2016-07-01  7:05           ` Wang Xiaoguang
2016-07-01  7:32             ` Eryu Guan
2016-06-23  9:15 ` [PATCH] btrfs: " 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=20160630135237.GG23649@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=wangxg.fnst@cn.fujitsu.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