Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 75EC3C4360F for ; Thu, 4 Apr 2019 09:25:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5093920449 for ; Thu, 4 Apr 2019 09:25:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387512AbfDDJZm (ORCPT ); Thu, 4 Apr 2019 05:25:42 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:6250 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2387524AbfDDJZj (ORCPT ); Thu, 4 Apr 2019 05:25:39 -0400 Received: from DGGEMS405-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 95787E0B23CEFB1F447A; Thu, 4 Apr 2019 17:25:37 +0800 (CST) Received: from huawei.com (10.90.53.225) by DGGEMS405-HUB.china.huawei.com (10.3.19.205) with Microsoft SMTP Server id 14.3.408.0; Thu, 4 Apr 2019 17:25:27 +0800 From: "zhangyi (F)" To: CC: , , , , Subject: [PATCH] ext4: add inode to ordered data list when extending file without block allocation Date: Thu, 4 Apr 2019 17:29:52 +0800 Message-ID: <1554370192-113254-1-git-send-email-yi.zhang@huawei.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.90.53.225] X-CFilter-Loop: Reflected Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org Currently we capture a NULL data exposure problem after a crash or poweroff when append writing a file in the data=ordered mode. The problem is that we were not add inode to the transaction's order data list when updating i_disksize without new block allocation no matter the delay allocated block feature is enabled or not. write jbd2 writeback append write in allocated block mark buffer dirty update i_disksize mark inode dirty commit transaction write inode (data exposure after a crash) write dirty buffer It's fine in the case of new block allocation because we do this job in ext4_map_blocks(). To fix this problem, this patch add inode to current transaction's order data list after new data is copied and needing update i_disksize in the case of no block allocation. Fixes: 06bd3c36a733ac ("ext4: fix data exposure after a crash") Fixes: f3b59291a69d0b ("ext4: remove calls to ext4_jbd2_file_inode() from delalloc write path") Signed-off-by: zhangyi (F) --- fs/ext4/inode.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c index b32a57b..5cfa066 100644 --- a/fs/ext4/inode.c +++ b/fs/ext4/inode.c @@ -1419,6 +1419,16 @@ static int ext4_write_end(struct file *file, if (i_size_changed || inline_data) ext4_mark_inode_dirty(handle, inode); + /* + * Updating i_disksize when extending file without block + * allocation, the newly written data where should be visible + * after transaction commit must be on transaction's ordered + * data list. + */ + if (copied && (i_size_changed & 0x2) && + ext4_should_order_data(inode)) + ext4_jbd2_inode_add_write(handle, inode); + if (pos + len > inode->i_size && ext4_can_truncate(inode)) /* if we have allocated more blocks and copied * less. We will have blocks allocated outside @@ -3185,6 +3195,15 @@ static int ext4_da_write_end(struct file *file, * bu greater than i_disksize.(hint delalloc) */ ext4_mark_inode_dirty(handle, inode); + + /* + * Updating i_disksize when extending file without + * block allocation, the newly written data where + * should be visible after transaction commit must + * be on transaction's ordered data list. + */ + if (ext4_should_order_data(inode)) + ext4_jbd2_inode_add_write(handle, inode); } } -- 2.7.4