From patchwork Tue Jun 18 14:21:10 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zhang Yi X-Patchwork-Id: 13702456 Received: from dggsgout11.his.huawei.com (dggsgout11.his.huawei.com [45.249.212.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3955315ECC7; Tue, 18 Jun 2024 14:22:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.51 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718720532; cv=none; b=drWQWtmJ7X54SVBsUS37DkPC2Mvf3kd6LLozd19Z0TqCWayDftzalht5ZTYqjCm7SxlEMsJLtkm6btamzzQXcXy6RP16FF03sd6O0Wjoehdzta/LLV1E3/9EYFSRutxo32HyTSQhOhtn62ienndif1CKUUdEfzCn5pWoSaWZwkQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718720532; c=relaxed/simple; bh=LnBOAdAMo9DcvA2jubekvPpg0dlB0zFEKx2YkEZOuEw=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=UQ4j0hPh6zLSj/gqldI08cMweWr5Fbq1T4fY4unkCrHcZwqbEfygcIHxLczlmzASt2AgZTo22GvfyYnbgqT1yvUoKsPIlenRiB4InnLAMemQs6DE4gdhuntEfiT1e9ZhZRHuRdGu0c+mAbps8rUhqkclnhEQG4yv2ucDXWplZq8= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=huaweicloud.com; spf=pass smtp.mailfrom=huaweicloud.com; arc=none smtp.client-ip=45.249.212.51 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=huaweicloud.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huaweicloud.com Received: from mail.maildlp.com (unknown [172.19.163.235]) by dggsgout11.his.huawei.com (SkyGuard) with ESMTP id 4W3TTZ6HXBz4f3nTS; Tue, 18 Jun 2024 22:21:54 +0800 (CST) Received: from mail02.huawei.com (unknown [10.116.40.128]) by mail.maildlp.com (Postfix) with ESMTP id A03591A0568; Tue, 18 Jun 2024 22:22:06 +0800 (CST) Received: from huaweicloud.com (unknown [10.175.104.67]) by APP4 (Coremail) with SMTP id gCh0CgB34A0ImHFmVDEoAQ--.31709S4; Tue, 18 Jun 2024 22:22:02 +0800 (CST) From: Zhang Yi To: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org Cc: linux-kernel@vger.kernel.org, djwong@kernel.org, hch@infradead.org, brauner@kernel.org, david@fromorbit.com, chandanbabu@kernel.org, jack@suse.cz, yi.zhang@huawei.com, yi.zhang@huaweicloud.com, chengzhihao1@huawei.com, yukuai3@huawei.com Subject: [PATCH -next v6 0/2] iomap/xfs: fix stale data exposure when truncating realtime inodes Date: Tue, 18 Jun 2024 22:21:10 +0800 Message-Id: <20240618142112.1315279-1-yi.zhang@huaweicloud.com> X-Mailer: git-send-email 2.39.2 Precedence: bulk X-Mailing-List: linux-xfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-CM-TRANSID: gCh0CgB34A0ImHFmVDEoAQ--.31709S4 X-Coremail-Antispam: 1UD129KBjvJXoWxCry3tFy5XFWktF1UurW5GFg_yoW5CF1UpF ZxK3yakr4Ut34fZ3s7Z3WDXr15CaykCrWUGFy7Gw4fCFn8Zr1xZr1vqa1FkFWjk3s7uFs0 vF4FvFyfCr1qyFJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvY14x267AKxVW8JVW5JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26F1j6w1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4U JVWxJr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Gc CE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0E 2Ix0cI8IcVAFwI0_JrI_JrylYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJV W8JwACjcxG0xvY0x0EwIxGrwACjI8F5VA0II8E6IAqYI8I648v4I1lFIxGxcIEc7CjxVA2 Y2ka0xkIwI1l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4 xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1q6r43 MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I 0E14v26r4j6F4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v2 6r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Gr0_Gr1UYxBIdaVFxhVjvjDU0xZFpf9x0J UZa9-UUUUU= X-CM-SenderInfo: d1lo6xhdqjqx5xdzvxpfor3voofrz/ Changes since v5: - Drop all the code about zeroing out the whole allocation unitsize on truncate down in xfs_setattr_size() as Christoph suggested, let's just fix this issue for RT file by converting tail blocks to unwritten now, and we could think about forced aligned extent and atomic write later until it needs, so only pick patch 6 and 8 in previous version, do some minor git log changes. Changes since v4: - Drop the first patch in v4 "iomap: zeroing needs to be pagecache aware" since this series is not strongly depends on it, that patch still needs furtuer analyse and also should add to handle the case of a pending COW extent that extends over a data fork hole. This is a big job, so let's fix the exposure stale data issue and brings back the changes in iomap_write_end() first, don't block the ext4 buffered iomap conversion. - In patch 1, drop the 'ifndef rem_u64'. - In patch 4, factor out a helper xfs_setattr_truncate_data() to handle the zero out, update i_size, write back and drop pagecache on truncate. - In patch 5, switch to use xfs_inode_alloc_unitsize() in xfs_itruncate_extents_flags(). - In patch 6, changes to reserve blocks for rtextsize > 1 realtime inodes on truncate down. - In patch 7, drop the unwritten convert threshold, always convert tail blocks to unwritten on truncate down realtime inodes. - Add patch 8 to bring back 'commit 943bc0882ceb ("iomap: don't increase i_size if it's not a write operation")'. Changes since v3: - Factor out a new helper to get the remainder in math64.h as Darrick suggested. - Adjust the truncating order to prevent too much redundant blocking writes as Dave suggested. - Improve to convert the tail extent to unwritten when truncating down an inode with large rtextsize as Darrick and Dave suggested. Since 'commit 943bc0882ceb ("iomap: don't increase i_size if it's not a write operation")' merged, Chandan reported a stale data exposure issue when running fstests generic/561 on xfs with realtime device [1]. This issue has been fix in 6.10 by revert this commit through commit '0841ea4a3b41 ("iomap: keep on increasing i_size in iomap_write_end()")', but the real problem is xfs_setattr_size() doesn't zero out enough range when truncate down a realtime inode. So this series fix this problem by just converting the tail blocks to unwritten when truncate down realtime inodes, then we could bring commit 943bc0882ceb back. I've tested this series on fstests (1) with reflink=0, (2) with reflink=1, (3) with 28K RT device, no new failures detected, and it passed generic/561 on RT device over 300+ rounds, please let me know if we need any other test. [1] https://lore.kernel.org/linux-xfs/87ttj8ircu.fsf@debian-BULLSEYE-live-builder-AMD64/ Thanks, Yi. Zhang Yi (2): xfs: reserve blocks for truncating large realtime inode iomap: don't increase i_size in iomap_write_end() fs/iomap/buffered-io.c | 53 +++++++++++++++++++++++------------------- fs/xfs/xfs_iops.c | 15 +++++++++++- 2 files changed, 43 insertions(+), 25 deletions(-) Reviewed-by: Darrick J. Wong