From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754053AbcKQBOX (ORCPT ); Wed, 16 Nov 2016 20:14:23 -0500 Received: from szxga01-in.huawei.com ([58.251.152.64]:60950 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753101AbcKQBOW (ORCPT ); Wed, 16 Nov 2016 20:14:22 -0500 Subject: Re: [PATCH] f2fs: fix fdatasync To: Christoph Hellwig References: <20161116121211.11790-1-yuchao0@huawei.com> <20161116121538.GA22373@infradead.org> CC: , , , From: Chao Yu Message-ID: <0148c188-5e03-432d-b03b-3e968364b5e4@huawei.com> Date: Thu, 17 Nov 2016 09:13:03 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20161116121538.GA22373@infradead.org> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016/11/16 20:15, Christoph Hellwig wrote: > On Wed, Nov 16, 2016 at 08:12:11PM +0800, Chao Yu wrote: >> For below two cases, we can't guarantee data consistence: >> >> a) >> 1. xfs_io "pwrite 0 4195328" "fsync" >> 2. xfs_io "pwrite 4195328 1024" "fdatasync" >> 3. godown >> 4. umount & mount >> --> isize we updated before fdatasync won't be recovered >> >> b) >> 1. xfs_io "pwrite -S 0xcc 0 4202496" "fsync" >> 2. xfs_io "fpunch 4194304 4096" "fdatasync" >> 3. godown >> 4. umount & mount >> --> dnode we punched before fdatasync won't be recovered > > Can you please add testcases for these to xfstests? It's OK, will do. > > . >