mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
	ke.wang@unisoc.com, Hao_hao.Wang@unisoc.com,
	baocong.liu@unisoc.com
Subject: Re: [PATCH 2/2] f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic
Date: Fri, 13 Jun 2025 13:48:52 +0800	[thread overview]
Message-ID: <4c7c12d3-4305-4756-9623-0154d7cce6c8@kernel.org> (raw)
In-Reply-To: <1749779445-29125-2-git-send-email-zhiguo.niu@unisoc.com>

On 2025/6/13 9:50, Zhiguo Niu wrote:
> The decompress_io_ctx may be released asynchronously after
> I/O completion. If this file is deleted immediately after read,
> and the kworker of processing post_read_wq has not been executed yet
> due to high workloads, It is possible that the inode(f2fs_inode_info)
> is evicted and freed before it is used f2fs_free_dic.
> 
>      The UAF case as below:
>      Thread A                                      Thread B
>      - f2fs_decompress_end_io
>       - f2fs_put_dic
>        - queue_work
>          add free_dic work to post_read_wq
>                                                     - do_unlink
>                                                      - iput
>                                                       - evict
>                                                        - call_rcu
>      This file is deleted after read.
> 
>      Thread C                                 kworker to process post_read_wq
>      - rcu_do_batch
>       - f2fs_free_inode
>        - kmem_cache_free
>       inode is freed by rcu
>                                               - process_scheduled_works
>                                                - f2fs_late_free_dic
>                                                 - f2fs_free_dic
>                                                  - f2fs_release_decomp_mem
>                                        read (dic->inode)->i_compress_algorithm
> 
> This patch store compress_algorithm and sbi in dic to avoid inode UAF.
> 
> In addition, the previous solution is deprecated in [1] may cause system hang.
> [1] https://lore.kernel.org/all/c36ab955-c8db-4a8b-a9d0-f07b5f426c3f@kernel.org
> 
> Cc: Daeho Jeong <daehojeong@google.com>
> Fixes: bff139b49d9f ("f2fs: handle decompress only post processing in softirq")
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
> Signed-off-by: Baocong Liu <baocong.liu@unisoc.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  reply	other threads:[~2025-06-13  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13  1:50 [PATCH 1/2] f2fs: compress: change the first parameter of page_array_{alloc,free} to sbi Zhiguo Niu
2025-06-13  1:50 ` [PATCH 2/2] f2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic Zhiguo Niu
2025-06-13  5:48   ` Chao Yu [this message]
2025-06-13  5:38 ` [PATCH 1/2] f2fs: compress: change the first parameter of page_array_{alloc,free} to sbi Chao Yu
2025-06-24  0:41 ` [f2fs-dev] [PATCH 1/2] f2fs: compress: change the first parameter of page_array_{alloc, free} " patchwork-bot+f2fs

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=4c7c12d3-4305-4756-9623-0154d7cce6c8@kernel.org \
    --to=chao@kernel.org \
    --cc=Hao_hao.Wang@unisoc.com \
    --cc=baocong.liu@unisoc.com \
    --cc=jaegeuk@kernel.org \
    --cc=ke.wang@unisoc.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niuzhiguo84@gmail.com \
    --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®