From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, zhiguo.niu@unisoc.com, stable@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid folio->mapping dereference in is_{meta, node}_folio()
Date: Mon, 14 Sep 2026 15:30:19 +0000 [thread overview]
Message-ID: <178939981988.647967.8103343136989536572.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910022026.3301257-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 10 Sep 2026 02:20:26 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> Otherwise, it may cause NULL pointer dereference in race condition:
>
> Thread A Thread B
> - f2fs_setattr
> - f2fs_truncate
> - f2fs_truncate_blocks
> - f2fs_do_truncate_blocks
> - f2fs_truncate_inode_blocks
> - truncate_dnode
> - truncate_node
> - invalidate_mapping_pages
> - folio->mapping = NULL
> - folio_lock
> - is_node_folio
> - F2FS_F_SB(folio): dereference on folio->mapping
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid folio->mapping dereference in is_{meta, node}_folio()
https://git.kernel.org/jaegeuk/f2fs/c/b5a71253c5c7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-14 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 2:20 [PATCH] f2fs: fix to avoid folio->mapping dereference in is_{meta,node}_folio() Chao Yu
2026-09-10 3:11 ` [f2fs-dev] [PATCH] f2fs: fix to avoid folio->mapping dereference in is_{meta, node}_folio() Zhiguo Niu
2026-09-10 21:26 ` Jaegeuk Kim
2026-09-11 0:18 ` Chao Yu
2026-09-11 1:07 ` Jaegeuk Kim
2026-09-11 1:13 ` Chao Yu
2026-09-14 15:30 ` patchwork-bot+f2fs [this message]
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=178939981988.647967.8103343136989536572.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=zhiguo.niu@unisoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®