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 8A8A23ECBE2 for ; Wed, 15 Apr 2026 16:51:06 +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=1776271866; cv=none; b=jUdc1juXGWoW1vlvsPRoI3PJOvcZCrGyvuOnUwCZBdxLnrMkWccuOYSyame+fbMfCh6MXg303CYxNRzACV78Hek47qSRbHm5HiT/aAlM82BjZ5FEc+btccMRV+04oJrqxAcu1Ubw0Y4x+Uo1KaGdIQsz6Feh21fwaO2ds9R1dz8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776271866; c=relaxed/simple; bh=35miVx0G08ePpBXqcA0ayzPFY+95aTgCfrayDKUEhOg=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=KyfRTfv6eAqFqBpfW5ORzsav6xr2w0Xy6720H43P45q3zofY8A7IccdcHd13jFTN42VGU20Dn/l2bWsYfQ1aG98MUHdJOj3ZB1q0qzgl8wrepwSYZseAiDZFvoRP11oLxgXr5Du9nUbiHPyMz+YbXz0pUuvhsRVSZ5dZjk5v7x8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=dg04ZZiE; 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="dg04ZZiE" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6EFB5C2BCB4; Wed, 15 Apr 2026 16:51:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776271866; bh=35miVx0G08ePpBXqcA0ayzPFY+95aTgCfrayDKUEhOg=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=dg04ZZiE+IcRk7+Q0cNZdKuJqq+CykO9VLGKxQBxvIOrwKuomWoiWDvLN5ai/Vzvb MRxAvo3AL2vqJ8vpL7hw/t/wFe0FFeNbmoFD4ysMQMKSXMwHO5cA3sBUMjC7fRu+H9 ztOTINdok80i3hAjmnPuNSwJtMW4yy5S0sN192+sz+FoYmSIXiYR+QRwrO/0BSgwIk 9eRWuwvgF+/3rm0D28JwJSxN9nXHw2NNm+Csz5IFGjL93pLgK+VfzaZQMZoJ4beb/q ESyx+pPhl2V0e8CJz0ae10Zofd6Ce7G07xz1gslw3pjNKbs/ba0y7iS/f4q2B8K6CP wIbi5xER7+9sA== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 34AF8380A964; Wed, 15 Apr 2026 16:50:37 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH] f2fs: fix node_cnt race between extent node destroy and writeback From: patchwork-bot+f2fs@kernel.org Message-Id: <177627183604.2303073.17250011751833572964.git-patchwork-notify@kernel.org> Date: Wed, 15 Apr 2026 16:50:36 +0000 References: <20260403144015.221811-3-monty_pavel@sina.com> In-Reply-To: <20260403144015.221811-3-monty_pavel@sina.com> To: Yongpeng Yang Cc: chao@kernel.org, jaegeuk@kernel.org, yangyongpeng@xiaomi.com, stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Fri, 3 Apr 2026 22:40:17 +0800 you wrote: > From: Yongpeng Yang > > f2fs_destroy_extent_node() does not set FI_NO_EXTENT before clearing > extent nodes. When called from f2fs_drop_inode() with I_SYNC set, > concurrent kworker writeback can insert new extent nodes into the same > extent tree, racing with the destroy and triggering f2fs_bug_on() in > __destroy_extent_node(). The scenario is as follows: > > [...] Here is the summary with links: - [f2fs-dev] f2fs: fix node_cnt race between extent node destroy and writeback https://git.kernel.org/jaegeuk/f2fs/c/ed78aeebef05 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html