From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: syzbot+b4444e3c972a7a124187@syzkaller.appspotmail.com,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid UAF in f2fs_write_end_io()
Date: Mon, 19 Jan 2026 13:50:46 +0000 [thread overview]
Message-ID: <176883064677.1419958.15115865034651314152.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260107112218.1789-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 7 Jan 2026 19:22:18 +0800 you wrote:
> As syzbot reported an use-after-free issue in f2fs_write_end_io().
>
> It is caused by below race condition:
>
> loop device umount
> - worker_thread
> - loop_process_work
> - do_req_filebacked
> - lo_rw_aio
> - lo_rw_aio_complete
> - blk_mq_end_request
> - blk_update_request
> - f2fs_write_end_io
> - dec_page_count
> - folio_end_writeback
> - kill_f2fs_super
> - kill_block_super
> - f2fs_put_super
> : free(sbi)
> : get_pages(, F2FS_WB_CP_DATA)
> accessed sbi which is freed
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid UAF in f2fs_write_end_io()
https://git.kernel.org/jaegeuk/f2fs/c/ce2739e482bc
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
next prev parent reply other threads:[~2026-01-19 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 11:22 [f2fs-dev] [PATCH] f2fs: fix to avoid UAF in f2fs_write_end_io() Chao Yu via Linux-f2fs-devel
2026-01-19 13:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-03-02 1:31 ` Guenter Roeck
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=176883064677.1419958.15115865034651314152.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@kernel.org \
--cc=syzbot+b4444e3c972a7a124187@syzkaller.appspotmail.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