Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp5203016rdb; Sat, 30 Dec 2023 10:02:50 -0800 (PST) X-Google-Smtp-Source: AGHT+IGJPfSZr7+Wq8MqLC/ip4wstjmvet5RLzJwRJT7js9HEZHpiVhbDbCOT7wX2jdoYq/BwxQZ X-Received: by 2002:a17:902:e5c2:b0:1d4:2f06:a2a2 with SMTP id u2-20020a170902e5c200b001d42f06a2a2mr6954246plf.58.1703959369924; Sat, 30 Dec 2023 10:02:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703959369; cv=none; d=google.com; s=arc-20160816; b=qFFsamVRLu4uIn/vBaQ2K+gO/1OkSHgGgh6jP0nRfz3/eLO0wYKaN9gJLcbYddJiHP ln9g20P8/58fda0YH0jX2R9Qy29pv7S705JaRNPQNEnuHJM0pgEDkMXc+E9iRGx5U5J9 Oxk/7+iV/znpB7AWX8BABvFpK3IyVAc450vqdtNSfFeQLjd+pXwMvNlS70KbG74KwwS1 i4HcxIQ5XZOExWIS4ZV6K5Iur0KcoB1hk+TvjqqabT8ylGig5ST038BpFDyaroG51yk8 tudL73RSMwmWDnxZjll8V5FKZE6zPwexWUphQCdN39e61asYAeP2zC1yRNX0W0ggeSEB txuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=mg4NEAtlIdMJsQ3DLm6kXqa/wV+e7FCzKtuVzxdonAU=; fh=MuvLizTYD37khvl3f/S2+VzSkx0yD4XVcaVgqLsymzI=; b=EIvV8qpQjJI+6Q2OxMcqU0sVHbiYDRQzdLDZ7uMFFDXDlNS2DsXC/gP+idfq2RVeM8 jFuY5+Vdj6O5zN02QS2qz70ugzL5QwzYuTuV2uuJsq8sUAo/ukQ3jPiykrIoN0zaoKeM //O6oeVdW/6T29wha5vqjejUNppZoSFEI4fbdseRvLvKKpECGX70wkXh5en0EwOBfMHM bW6Q5rHvBm2kzkHvLUA6Pc4ckg198ha85cqYIB2DzVhtm1BmVCQnKE8GZvHKuZWb31Ql 47/rRq5A9qsTirjUE4R9QKxJvB1ndarwan0uamnQASumHp1mu0YaId+nhr1qCtiyjz48 /lvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=OF+JWlNJ; spf=pass (google.com: domain of linux-kernel+bounces-13563-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-13563-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id h9-20020a170902f7c900b001d49a084969si3354555plw.372.2023.12.30.10.02.49 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 30 Dec 2023 10:02:49 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-13563-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=OF+JWlNJ; spf=pass (google.com: domain of linux-kernel+bounces-13563-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-13563-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 8B768283F2A for ; Sat, 30 Dec 2023 18:02:49 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id B7E05BE58; Sat, 30 Dec 2023 18:02:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="OF+JWlNJ" X-Original-To: linux-kernel@vger.kernel.org Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (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 43CD5BA37; Sat, 30 Dec 2023 18:02:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org 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=mg4NEAtlIdMJsQ3DLm6kXqa/wV+e7FCzKtuVzxdonAU=; b=OF+JWlNJMC8/3tu2Szw4PK/Ar0 5ey8YqWRAtAv2ZPHLGNnOKWZ4kZqbPXaN6M6v1zEI7L2qPhhwfbR5fkYIF1577WQXcdwEqymggxga 0LAMzWx+nLz27hbMyWfQWxtP+1ebGkRL2fHtJjFi0Tn9W2W0RmDHpkYlxfnmfofHR5HUeeozGAJRr N1H3Jl08EL9sE/e+0ZYmT+XvqIXMdwgv2XKLSmLhpj7CB1NhLCeAsylVYa1bFFrM5JK34wWIUwhIN kASApqY2fx2FjZyRUidkpOxyNJ4LM9U2ni7HI1LE5tJXUk6KIKabqeDRzBTJo+lsYwlLMgqP1IVVF etclSpgg==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1rJdfK-007C9z-VU; Sat, 30 Dec 2023 18:02:31 +0000 Date: Sat, 30 Dec 2023 18:02:30 +0000 From: Matthew Wilcox To: Genes Lists Cc: linux-kernel@vger.kernel.org, Andrew Morton , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org Subject: Re: 6.6.8 stable: crash in folio_mark_dirty Message-ID: References: <8bb29431064fc1f70a42edef75a8788dd4a0eecc.camel@sapience.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8bb29431064fc1f70a42edef75a8788dd4a0eecc.camel@sapience.com> On Sat, Dec 30, 2023 at 10:23:26AM -0500, Genes Lists wrote: > Apologies in advance, but I cannot git bisect this since machine was > running for 10 days on 6.6.8 before this happened. Thanks for the report. Apologies, I'm on holiday until the middle of the week so this will be extremely terse. > - Root, efi is on nvme > - Spare root,efi is on sdg > - md raid6 on sda-sd with lvmcache from one partition on nvme drive. > - all filesystems are ext4 (other than efi). > - 32 GB mem. > Dec 30 07:00:36 s6 kernel: ------------[ cut here ]------------ > Dec 30 07:00:36 s6 kernel: WARNING: CPU: 0 PID: 521524 at mm/page-writeback.c:2668 __folio_mark_dirty (??:?) This is: WARN_ON_ONCE(warn && !folio_test_uptodate(folio)); > Dec 30 07:00:36 s6 kernel: CPU: 0 PID: 521524 Comm: rsync Not tainted 6.6.8-stable-1 #13 d238f5ab6a206cdb0cc5cd72f8688230f23d58df So rsync is exiting. Do you happen to know what rsync is doing? > Dec 30 07:00:36 s6 kernel: block_dirty_folio (??:?) > Dec 30 07:00:36 s6 kernel: unmap_page_range (??:?) > Dec 30 07:00:36 s6 kernel: unmap_vmas (??:?) > Dec 30 07:00:36 s6 kernel: exit_mmap (??:?) > Dec 30 07:00:36 s6 kernel: __mmput (??:?) > Dec 30 07:00:36 s6 kernel: do_exit (??:?) > Dec 30 07:00:36 s6 kernel: do_group_exit (??:?) > Dec 30 07:00:36 s6 kernel: __x64_sys_exit_group (??:?) > Dec 30 07:00:36 s6 kernel: do_syscall_64 (??:?) It looks llike rsync has a page from the block device mmaped? I'll have to investigate this properly when I'm back. If you haven't heard from me in a week, please ping me. (I don't think I caused this, but I think I stand a fighting chance of tracking down what the problem is, just not right now).