From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yongpeng Yang <monty_pavel@sina.com>
Cc: jaegeuk@kernel.org, yangyongpeng@xiaomi.com,
stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix node_cnt race between extent node destroy and writeback
Date: Wed, 15 Apr 2026 16:50:36 +0000 [thread overview]
Message-ID: <177627183604.2303073.17250011751833572964.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260403144015.221811-3-monty_pavel@sina.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 3 Apr 2026 22:40:17 +0800 you wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
>
> 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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Yongpeng Yang <monty_pavel@sina.com>
Cc: chao@kernel.org, jaegeuk@kernel.org, yangyongpeng@xiaomi.com,
stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix node_cnt race between extent node destroy and writeback
Date: Wed, 15 Apr 2026 16:50:36 +0000 [thread overview]
Message-ID: <177627183604.2303073.17250011751833572964.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260403144015.221811-3-monty_pavel@sina.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 3 Apr 2026 22:40:17 +0800 you wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
>
> 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
next prev parent reply other threads:[~2026-04-15 16:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 14:40 [f2fs-dev] [PATCH] f2fs: fix node_cnt race between extent node destroy and writeback Yongpeng Yang
2026-04-03 14:40 ` Yongpeng Yang
2026-04-13 11:23 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-04-13 11:23 ` Chao Yu
2026-04-15 16:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-04-15 16:50 ` [f2fs-dev] " patchwork-bot+f2fs
2026-04-17 9:00 ` Chao Yu via Linux-f2fs-devel
2026-04-17 9:00 ` Chao Yu
2026-04-17 13:26 ` [f2fs-dev] " Yongpeng Yang
2026-04-17 13:26 ` Yongpeng Yang
2026-04-18 0:51 ` Chao Yu via Linux-f2fs-devel
2026-04-18 0:51 ` Chao Yu
2026-04-18 16:29 ` Yongpeng Yang
2026-04-18 16:29 ` Yongpeng Yang
2026-04-20 7:28 ` Chao Yu via Linux-f2fs-devel
2026-04-20 7:28 ` Chao Yu
2026-04-21 8:44 ` Yongpeng Yang
2026-04-21 8:44 ` Yongpeng Yang
2026-04-21 9:04 ` Chao Yu via Linux-f2fs-devel
2026-04-21 9:04 ` Chao Yu
2026-04-21 21:52 ` Jaegeuk Kim via Linux-f2fs-devel
2026-04-21 21:52 ` Jaegeuk Kim
2026-04-22 7:01 ` Yongpeng Yang
2026-04-22 7:01 ` Yongpeng Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177627183604.2303073.17250011751833572964.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=monty_pavel@sina.com \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yangyongpeng@xiaomi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.