mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, daehojeong@google.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: atomic: fix UAF issue on f2fs_inode_info.atomic_inode
Date: Fri, 22 May 2026 04:30:06 +0000	[thread overview]
Message-ID: <177942420615.624124.15880655072071965222.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260521021505.1357466-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Thu, 21 May 2026 10:15:05 +0800 you wrote:
> - ioctl(F2FS_IOC_GARBAGE_COLLECT_RANGE)		- shrink
>  - f2fs_gc
>   - gc_data_segment
>    - ra_data_block(cow_inode)
>     - mapping = F2FS_I(inode)->atomic_inode->i_mapping
>     : f2fs_is_cow_file(cow_inode) is true
> 						 - f2fs_evict_inode(atomic_inode)
> 						  - clear_inode_flag(fi->cow_inode, FI_COW_FILE)
> 						  - F2FS_I(fi->cow_inode)->atomic_inode = NULL
> 						  ...
> 						  - truncate_inode_pages_final(atomic_inode)
>     - f2fs_grab_cache_folio(mapping)
>     : create folio in atomic_inode->mapping
> 						  - clear_inode(atomic_inode)
> 						   - BUG_ON(atomic_inode->i_data.nrpages)
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: atomic: fix UAF issue on f2fs_inode_info.atomic_inode
    https://git.kernel.org/jaegeuk/f2fs/c/6a59aa5442e3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-05-22  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  2:15 Chao Yu
2026-05-22  4: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=177942420615.624124.15880655072071965222.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=daehojeong@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /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
Powered by JetHome