Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752213AbbFEKfN (ORCPT ); Fri, 5 Jun 2015 06:35:13 -0400 Received: from mailout1.samsung.com ([203.254.224.24]:49135 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751422AbbFEKfI (ORCPT ); Fri, 5 Jun 2015 06:35:08 -0400 X-AuditID: cbfee61a-f79516d000006302-f9-55717b5abaac From: Chao Yu To: Jaegeuk Kim Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: [PATCH] f2fs: do not trim preallocated blocks when truncating after i_size Date: Fri, 05 Jun 2015 18:34:02 +0800 Message-id: <000101d09f7b$4a2559e0$de700da0$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AdCfdok9etRkOXWsQnia9ce1YHo1QQ== Content-language: zh-cn X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsVy+t9jQd2o6sJQg2N7LS2erJ/FbHFpkbvF 5V1z2ByYPTat6mTz2L3gM5PH501yAcxRXDYpqTmZZalF+nYJXBnbO3tZC87wVuw/d5KpgfEs VxcjJ4eEgInEokWTmCFsMYkL99azgdhCAtMZJT4cZ+xi5AKyXzFKHP7TzAqSYBNQkVje8Z8J xBYBsg8tuswOYjMLeEg0dnwHquHgEBYIlXh7zxckzCKgKvHlyQ6wcl4BS4l5ExoZIWxBiR+T 77FAtGpJrN95nAnClpfYvOYt1D0KEjvOvmaEWKUnsWzbDKh6cYmNR26xTGAUmIVk1Cwko2Yh GTULScsCRpZVjKKpBckFxUnpuYZ6xYm5xaV56XrJ+bmbGMHB+0xqB+PKBotDjAIcjEo8vA2G haFCrIllxZW5hxglOJiVRHiLK4BCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeU/m+4QKCaQnlqRm p6YWpBbBZJk4OKUaGNtCzrIE/jvM9sZruuYlW/tXr0KbGW6577+96HN2xsrT/BlVtjv7nsYZ 7zNcKbru0hrj6FOG8q6vLyYXLl13uDjy9sSMUL1jtZN27C6VMeGx5bJlCPicN3lBlMFiiavd /45P8zp5Rphp/9Zr9w7MzYqse3Dkicmy953bP5UIv791oEitz1BsPoMSS3FGoqEWc1FxIgDk xsy2WgIAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1928 Lines: 62 When we perform generic/092 in xfstests, output is like below: XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec) 0: [0..10239]: data 0: [0..10239]: data -1: [10240..20479]: unwritten +1: [10240..14335]: unwritten This is because with this testcase, we redefine the regulation for truncate in perallocated space past i_size as below: "There was some confused about what the fs was supposed to do when you truncate at i_size with preallocated space past i_size. We decided on the following things. 1) truncate(i_size) will trim all blocks past i_size. 2) truncate(x) where x > i_size will not trim all blocks past i_size. " This method is used in xfs, and then ext4/btrfs will follow the rule. This patch fixes to follow the new rule for f2fs. Signed-off-by: Chao Yu --- fs/f2fs/file.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 4d42d66..85f97af 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -651,16 +651,16 @@ int f2fs_setattr(struct dentry *dentry, struct iattr *attr) f2fs_get_encryption_info(inode)) return -EACCES; - if (attr->ia_size != i_size_read(inode)) { + if (attr->ia_size <= i_size_read(inode)) { truncate_setsize(inode, attr->ia_size); f2fs_truncate(inode); f2fs_balance_fs(F2FS_I_SB(inode)); } else { /* - * giving a chance to truncate blocks past EOF which - * are fallocated with FALLOC_FL_KEEP_SIZE. + * do not trim all blocks after i_size if target size is + * larger than i_size. */ - f2fs_truncate(inode); + truncate_setsize(inode, attr->ia_size); } } -- 2.4.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/