From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 96900C4332F for ; Sat, 19 Nov 2022 20:20:41 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1CAC76B0072; Sat, 19 Nov 2022 15:20:41 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 17B1D6B0073; Sat, 19 Nov 2022 15:20:41 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0428180007; Sat, 19 Nov 2022 15:20:40 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id E9C846B0072 for ; Sat, 19 Nov 2022 15:20:40 -0500 (EST) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id B64691C627F for ; Sat, 19 Nov 2022 20:20:40 +0000 (UTC) X-FDA: 80151309840.24.ECF9B24 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf02.hostedemail.com (Postfix) with ESMTP id 5054180006 for ; Sat, 19 Nov 2022 20:20:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=T0PEwCj46l8kkuAlr919hhJp7yTxS0xQb6cN9Cx/y8Q=; b=sl2rXH8kIZnL9wKiQp7DPMlcAM L7kNckDKmOoE1H6KAqu8TOnsaxkJdasnwxOqw7k3QThDsRvbG2ZsU0ppbJ+b1m7lXhhML2GQGvEW7 1mpWkAPLtX1cVL1XeeQQE57RVorfa2eR9kc3IcniZwC8/BmxNpRiAVNOa1y6gvVG/GrvKWUdp2Iax KuW43K0dBTs7LredAr2L0LJ8cHTUF94gTrV1DKz4nIr2BQSAUK3sbSCy1W+L6XXHYJ/srcYjlapo0 176dw34x996vRvVQIqko6uMzcWfvKZKCwBNNulzbjdc2ohdbnXHNyQP8xRVc5Yb7Am+4gmkG8Hn/e y2c2M7JA==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1owUKA-003WVF-H8; Sat, 19 Nov 2022 20:20:26 +0000 Date: Sat, 19 Nov 2022 20:20:26 +0000 From: Matthew Wilcox To: hev Cc: Hugh Dickins , Guoqi , Huacai Chen , linux-mm@kvack.org, Linux Kernel Mailing List , Rui Wang Subject: Re: [RFC PATCH] mm/shmem: Fix undo range for failed fallocate Message-ID: References: <20221101032248.819360-1-kernel@hev.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1668889240; a=rsa-sha256; cv=none; b=oxl1YKNVHULJKfDiuPKv+K8qMb1jYxhkQ8w2QWP84BrXRu9/IYtdfPYehgNg6MnLLGaBNs uHaJuRINevTBtAoOAFTVWG3oX2Tw7nTgYtxuUCBRct2e0H1lQPE6TyeE9KuNS40ZnXf23k 5xe9hke8OHS5zkGZCFWt1hg1DWcE380= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=sl2rXH8k; dmarc=none; spf=none (imf02.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1668889240; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=T0PEwCj46l8kkuAlr919hhJp7yTxS0xQb6cN9Cx/y8Q=; b=hRxZxwStfXmPOCs9P15bYiB4BVgM3ZHr4O3CqZrFO3jCNbV8eaEGbWfW9JYXvSj3Ft0VPa 2AjsY8krNcYKpFKznBzpvejrTdp9zV18cvuyfUVIqEpkbsHjcH81Asm08TKNhA6hlkkLAi FP0nKx8eEJOTxcRMvlJny+8zAXZG9AQ= X-Rspam-User: X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: 5054180006 Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=sl2rXH8k; dmarc=none; spf=none (imf02.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org X-Stat-Signature: tmhch7r8gmxnrgwag8tgrr84dfrkdx9s X-HE-Tag: 1668889239-90298 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Sat, Nov 19, 2022 at 10:45:52PM +0800, hev wrote: > Ping I'll be back on Wednesday and will look then. > On Thu, Nov 3, 2022 at 3:52 PM hev wrote: > > > > Hi Matthew, > > > > On Wed, Nov 2, 2022 at 10:41 PM Matthew Wilcox wrote: > > > > > > On Tue, Nov 01, 2022 at 11:22:48AM +0800, Rui Wang wrote: > > > > This patch fixes data loss caused by the fallocate system > > > > call interrupted by a signal. > > > > > > > > Bug: https://lore.kernel.org/linux-mm/33b85d82.7764.1842e9ab207.Coremail.chenguoqic@163.com/ > > > > Fixes: b9a8a4195c7d ("truncate,shmem: Handle truncates that split large folios") > > > > > > How does that commit introduce this bug? > > > > In the test case[1], we created a file that contains non-zero data > > from offset 0 to A-1. and a process try to expand this file by > > fallocate(fd, 0, 0, B), B > A. > > Concurrently, another process try to interrupt this fallocate syscall > > by a signal. I think the expected results are: > > > > 1. The file is not expanded and file size is A, and the data from > > offset 0 to A-1 is not changed. > > 2. The file is expanded and the data from offset 0 to A-1 is not > > changed, and from A to B-1 contains zeros. > > > > Now, the unexpected result is that the file is not expanded and the > > data that from offset 0 to A-1 is changed by > > truncate_inode_partial_folio that called > > from shmem_undo_range with unfalloc = true. > > > > This issue is only reproduced when file on tmpfs, and begin from this > > commit: b9a8a4195c7d ("truncate,shmem: Handle truncates that split > > large folios") > > > > > > > > > Reported-by: Guoqi Chen > > > > Cc: Huacai Chen > > > > Signed-off-by: Rui Wang > > > > --- > > > > mm/shmem.c | 20 ++++++++++++-------- > > > > 1 file changed, 12 insertions(+), 8 deletions(-) > > > > > > > > diff --git a/mm/shmem.c b/mm/shmem.c > > > > index bc9b84602eec..8c8dce34eafc 100644 > > > > --- a/mm/shmem.c > > > > +++ b/mm/shmem.c > > > > @@ -948,11 +948,13 @@ static void shmem_undo_range(struct inode *inode, loff_t lstart, loff_t lend, > > > > folio = shmem_get_partial_folio(inode, lstart >> PAGE_SHIFT); > > > > if (folio) { > > > > same_folio = lend < folio_pos(folio) + folio_size(folio); > > > > - folio_mark_dirty(folio); > > > > - if (!truncate_inode_partial_folio(folio, lstart, lend)) { > > > > - start = folio->index + folio_nr_pages(folio); > > > > - if (same_folio) > > > > - end = folio->index; > > > > + if (!unfalloc || !folio_test_uptodate(folio)) { > > > > + folio_mark_dirty(folio); > > > > + if (!truncate_inode_partial_folio(folio, lstart, lend)) { > > > > + start = folio->index + folio_nr_pages(folio); > > > > + if (same_folio) > > > > + end = folio->index; > > > > + } > > > > > > ... so what you're saying is that if we allocate a page, but zeroing > > > it is interrupted by a signal, we cannot now remove that page from > > > the cache? That seems wrong. > > > > > > Surely the right solution is to remove this page from the cache if we're > > > interrupted by a signal. > > > > So I think we should not truncate_inode_partial_folio for unfalloc = > > true. Isn't that right? > > > > [1] https://github.com/abner-chenc/abner/blob/master/fallocate.c > > > > Regards, > > Ray >