From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 2172CB65C for ; Sat, 25 Jan 2025 01:20:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737768005; cv=none; b=hF9QxRfsp6Wys463W+Fks/EThx+IbaVIhFR++/CeYjUjG8Qk15Ul8JsqNkTPmwl7UJ3D4tS77+vzsQnBocXi4zaIgjZHRCf4NAcXV2KjhvLJlY3e4y4ZcnwPheDMOIWycPKRUG6c/A57hnywAmlzocHQa+OXyjRhxewAgTjfEGs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737768005; c=relaxed/simple; bh=nutvGNIkKEz4gbsW7HF0bd5iw8lyBvTI3VbocdOzGFo=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=rox1R4uaf6+NZtndHvU2oQpEUN/JZV9FlIKoieDAacbthNhOjcn8QMUF/cxbCLogIcrF6MNtS8cphyQDyXXz3Ju+z4gHJ+O3ix0Y0Bs47Csrua6lDFNBbD/MBBH6B08CjSKPcvUG1gGrXw92BDtq2fbIrWeDO3yTr3GjFHkyIA4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gsoere13; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gsoere13" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 89524C4CEE1; Sat, 25 Jan 2025 01:20:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1737768004; bh=nutvGNIkKEz4gbsW7HF0bd5iw8lyBvTI3VbocdOzGFo=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=gsoere13jSFyZ0Ep2YyPcV5lFnzVlNYlW0Ag2tmtOe6lz8crgoDxdKFh1uWDihtYO W2LovnW3W6PFDNdbBxhEO1ASzQINwHSBbAM+ahttqqtVFyG3EZ+a6ryN530C6kYEWD pKBNMp7MbJcIRSlKG0pJh3Yx/DkP/lanS0lFmI4Zq5g2QeuyLBK35IJllRpJ99w2/w lTEX/7nBspZv9zJRoEVaqsHjMHHRnWpyAFXNE3pct3z1CmMrdOA5afj3hyAmjdeCTu 358hPuqHJry4RL61nTOGHWszBZNCgMVff18YfN0g4OAKM2Zx++imfClIEuZPt8KH5E L/T8rGRY+G3Ew== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id AE0F9380AA79; Sat, 25 Jan 2025 01:20:30 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix inconsistent dirty state of atomic file From: patchwork-bot+f2fs@kernel.org Message-Id: <173776802950.2231594.13552564580598358004.git-patchwork-notify@kernel.org> Date: Sat, 25 Jan 2025 01:20:29 +0000 References: <20250124055751.283198-1-huangjianan@xiaomi.com> In-Reply-To: <20250124055751.283198-1-huangjianan@xiaomi.com> To: Jianan Huang Cc: linux-f2fs-devel@lists.sourceforge.net, chao@kernel.org, jaegeuk@kernel.org, daehojeong@google.com, jnhuang95@gmail.com, linux-kernel@vger.kernel.org, wanghui33@xiaomi.com, yudongbin@xiaomi.com Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Fri, 24 Jan 2025 13:57:51 +0800 you wrote: > When testing the atomic write fix patches, the f2fs_bug_on was > triggered as below: > > ------------[ cut here ]------------ > kernel BUG at fs/f2fs/inode.c:935! > Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI > CPU: 3 UID: 0 PID: 257 Comm: bash Not tainted 6.13.0-rc1-00033-gc283a70d3497 #5 > RIP: 0010:f2fs_evict_inode+0x50f/0x520 > Call Trace: > > ? __die_body+0x65/0xb0 > ? die+0x9f/0xc0 > ? do_trap+0xa1/0x170 > ? f2fs_evict_inode+0x50f/0x520 > ? f2fs_evict_inode+0x50f/0x520 > ? handle_invalid_op+0x65/0x80 > ? f2fs_evict_inode+0x50f/0x520 > ? exc_invalid_op+0x39/0x50 > ? asm_exc_invalid_op+0x1a/0x20 > ? __pfx_f2fs_get_dquots+0x10/0x10 > ? f2fs_evict_inode+0x50f/0x520 > ? f2fs_evict_inode+0x2e5/0x520 > evict+0x186/0x2f0 > prune_icache_sb+0x75/0xb0 > super_cache_scan+0x1a8/0x200 > do_shrink_slab+0x163/0x320 > shrink_slab+0x2fc/0x470 > drop_slab+0x82/0xf0 > drop_caches_sysctl_handler+0x4e/0xb0 > proc_sys_call_handler+0x183/0x280 > vfs_write+0x36d/0x450 > ksys_write+0x68/0xd0 > do_syscall_64+0xc8/0x1a0 > ? arch_exit_to_user_mode_prepare+0x11/0x60 > ? irqentry_exit_to_user_mode+0x7e/0xa0 > > [...] Here is the summary with links: - [f2fs-dev,v3] f2fs: fix inconsistent dirty state of atomic file https://git.kernel.org/jaegeuk/f2fs/c/03511e936916 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html