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 lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CB287C7619A for ; Wed, 5 Apr 2023 20:48:02 +0000 (UTC) Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1pkA2x-0003hK-Ct; Wed, 05 Apr 2023 20:48:00 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1pkA2w-0003hD-2E for linux-f2fs-devel@lists.sourceforge.net; Wed, 05 Apr 2023 20:47:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; 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:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=r4qMDxguIGRezRwQrXTGNuFRYn2+W6NvXNXp/KOdjYU=; b=Ct1NygZL3Ie4In/4b8RiY+FM4r NlFgtPOFWgPPw7cEDvKuqJkuViFW/s5/88mKzuiQdgQQN31/9+uA+jecb8m6CC9CIA8xaLm+nzzqi xmW9kH/6SkriSedOrAgoJOXvUjtWMZdFAQhhJgV/HJSC95UNNDNQMGpLhvnJFMcSbzs4=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; 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:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=r4qMDxguIGRezRwQrXTGNuFRYn2+W6NvXNXp/KOdjYU=; b=etrkq5QR+HjTkkL1WjtDhv2TEL EeQRREZMSrgSHZlCyvL2djwvZVJ54uR7jTCjUZQXmiF87zKrv3Kam+Btf8PD9w9qw+2ZMH3ohm2ys 2KJRrxo80gbV8z6p3DB1A15OWB0Nt9gyFGnYk03sIlmtHRe7LR39J/Iy2xY4vC2sJ6Yw=; Received: from dfw.source.kernel.org ([139.178.84.217]) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1pkA2v-00GHah-Ct for linux-f2fs-devel@lists.sourceforge.net; Wed, 05 Apr 2023 20:47:58 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 329E7629CA; Wed, 5 Apr 2023 20:47:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 62061C433EF; Wed, 5 Apr 2023 20:47:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1680727666; bh=JHYkzEFJehfbG4+KRCg90sRcADee5WmNO6JSJDaA3UI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KcHIC6dk/n3uDrmqf2bu7zCEr2DJ28jvt/zGKEVORnaPu5cmB/PPFR8mfpeGN/do5 NpDaLZ7zP7rS5/zBniaVT8rxVDJz5wXWVpsnD8PD55oeh8HNwDMGQ3lFXXFM48ZVIa pzzusqmdFST6v5G6DN5KPM87zqTQHjI3D1oRsUfoPiput1EuVKhDSNPDMQ6E7NLqe+ 6YsQ4khuyLr0TT78b3fBh/Uxkv0Aaw+JUOkc2MBPgOkEc86xCee7NYch51aJntyXX1 wo75tXqHKzWTaLjc8F8sc+bDJbnDcWD/7S1KDhL7Jrffne5O14KVvejg72d2xpuAGJ WisliDXJc8UyA== Date: Wed, 5 Apr 2023 13:47:44 -0700 From: Jaegeuk Kim To: Matthew Wilcox Message-ID: References: <20230323213919.1876157-1-jaegeuk@kernel.org> <8aea02b0-86f9-539a-02e9-27b381e68b66@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Headers-End: 1pkA2v-00GHah-Ct Subject: Re: [f2fs-dev] [PATCH] f2fs: get out of a repeat loop when getting a locked data page X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net On 04/05, Jaegeuk Kim wrote: > On 03/27, Matthew Wilcox wrote: > > On Mon, Mar 27, 2023 at 08:30:33AM -0700, Jaegeuk Kim wrote: > > > On 03/26, Chao Yu wrote: > > > > On 2023/3/24 5:39, Jaegeuk Kim wrote: > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=216050 > > > > > > > > > > Somehow we're getting a page which has a different mapping. > > > > > Let's avoid the infinite loop. > > > > > > > > > > Cc: > > > > > Signed-off-by: Jaegeuk Kim > > > > > --- > > > > > fs/f2fs/data.c | 8 ++------ > > > > > 1 file changed, 2 insertions(+), 6 deletions(-) > > > > > > > > > > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c > > > > > index bf51e6e4eb64..80702c93e885 100644 > > > > > --- a/fs/f2fs/data.c > > > > > +++ b/fs/f2fs/data.c > > > > > @@ -1329,18 +1329,14 @@ struct page *f2fs_get_lock_data_page(struct inode *inode, pgoff_t index, > > > > > { > > > > > struct address_space *mapping = inode->i_mapping; > > > > > struct page *page; > > > > > -repeat: > > > > > + > > > > > page = f2fs_get_read_data_page(inode, index, 0, for_write, NULL); > > > > > if (IS_ERR(page)) > > > > > return page; > > > > > /* wait for read completion */ > > > > > lock_page(page); > > > > > - if (unlikely(page->mapping != mapping)) { > > > > > > > > How about using such logic only for move_data_page() to limit affect for > > > > other paths? > > > > > > Why move_data_page() only? If this happens, we'll fall into a loop in anywhere? > > > > > > > > > > > Jaegeuk, any thoughts about why mapping is mismatch in between page's one and > > > > inode->i_mapping? > > > > > > > > > > > After several times code review, I didn't get any clue about why f2fs always > > > > get the different mapping in a loop. > > > > > > I couldn't find the path to happen this. So weird. Please check the history in the > > > bug. > > > > > > > > > > > Maybe we can loop MM guys to check whether below folio_file_page() may return > > > > page which has different mapping? > > > > > > Matthew may have some idea on this? > > > > There's a lot of comments in the bug ... hard to come into this one > > cold. > > > > I did notice this one (#119): > > : Interestingly, ref count is 514, which looks suspiciously as a binary > > : flag 1000000010. Is it possible that during 5.17/5.18 implementation > > : of a "pin", somehow binary flag was written to ref count, or something > > : like '1 << ...' happens? > > > > That indicates to me that somehow you've got hold of a THP that is in > > the page cache. Probably shmem/tmpfs. That indicate to me a refcount > > problem that looks something like this: > > > > f2fs allocates a page > > f2fs adds the page to the page cache > > f2fs puts the reference to the page without removing it from the > > page cache (how?) > > Is it somewhat related to setting a bit in private field? > > When we migrate the blocks, we do: > 1) get_lock_page() > 2) submit read > 3) lock_page() > 3) set_page_dirty() > 4) set_page_private_gcing(page) > > --- in fs/f2fs/f2fs.h > 1409 #define PAGE_PRIVATE_SET_FUNC(name, flagname) \ > 1410 static inline void set_page_private_##name(struct page *page) \ > 1411 { \ > 1412 if (!PagePrivate(page)) { \ > 1413 get_page(page); \ > 1414 SetPagePrivate(page); \ > 1415 set_page_private(page, 0); \ > 1416 } \ > 1417 set_bit(PAGE_PRIVATE_NOT_POINTER, &page_private(page)); \ > 1418 set_bit(PAGE_PRIVATE_##flagname, &page_private(page)); \ > 1419 } > > > 5) set_page_writebac() > 6) submit write > 7) unlock_page() > 8) put_page(page) > > Later, f2fs_invalidate_folio will do put_page again by: > clear_page_private_gcing(&folio->page); > > --- in fs/f2fs/f2fs.h > 1421 #define PAGE_PRIVATE_CLEAR_FUNC(name, flagname) \ > 1422 static inline void clear_page_private_##name(struct page *page) \ > 1423 { \ > 1424 clear_bit(PAGE_PRIVATE_##flagname, &page_private(page)); \ > 1425 if (page_private(page) == BIT(PAGE_PRIVATE_NOT_POINTER)) { \ > 1426 set_page_private(page, 0); \ > 1427 if (PagePrivate(page)) { \ > 1428 ClearPagePrivate(page); \ > 1429 put_page(page); \ > 1430 }\ > 1431 } \ > 1432 } It seems f2fs_invalidate_folio and f2fs_release_folio drop the refcount by folio_detach_private() additionally. https://lore.kernel.org/lkml/20230405204321.2056498-1-jaegeuk@kernel.org/T/#u > > > page is now free, gets reallocated into a THP > > lookup from the f2fs file finds the new THP > > things explode messily > > > > Checking page->mapping is going to avoid the messy explosion, but > > you'll still have a page in the page cache which doesn't actually > > belong to you, and that's going to lead to subtle data corruption. > > > > This should be caught by page_expected_state(), called from > > free_page_is_bad(), called from free_pages_prepare(). Do your testers > > have CONFIG_DEBUG_VM enabled? That might give you a fighting chance at > > finding the last place which called put_page(). It won't necessarily be > > the _wrong_ place to call put_page() (that may have happened earlier), > > but it may give you a clue. > > > > > > > > > > struct page *pagecache_get_page(struct address_space *mapping, pgoff_t index, > > > > int fgp_flags, gfp_t gfp) > > > > { > > > > struct folio *folio; > > > > > > > > folio = __filemap_get_folio(mapping, index, fgp_flags, gfp); > > > > if (IS_ERR(folio)) > > > > return NULL; > > > > return folio_file_page(folio, index); > > > > } > > > > > > > > Thanks, > > > > > > > > > - f2fs_put_page(page, 1); > > > > > - goto repeat; > > > > > - } > > > > > - if (unlikely(!PageUptodate(page))) { > > > > > + if (unlikely(page->mapping != mapping || !PageUptodate(page))) { > > > > > f2fs_put_page(page, 1); > > > > > return ERR_PTR(-EIO); > > > > > } _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel