From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix to avoid mmap vs set_compress_option case
Date: Mon, 17 Jul 2023 17:34:21 +0000 [thread overview]
Message-ID: <168961526181.4078.12987776501092675695.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230706020614.2950782-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 6 Jul 2023 10:06:14 +0800 you wrote:
> Compression option in inode should not be changed after they have
> been used, however, it may happen in below race case:
>
> Thread A Thread B
> - f2fs_ioc_set_compress_option
> - check f2fs_is_mmap_file()
> - check get_dirty_pages()
> - check F2FS_HAS_BLOCKS()
> - f2fs_file_mmap
> - set_inode_flag(FI_MMAP_FILE)
> - fault
> - do_page_mkwrite
> - f2fs_vm_page_mkwrite
> - f2fs_get_block_locked
> - fault_dirty_shared_page
> - set_page_dirty
> - update i_compress_algorithm
> - update i_log_cluster_size
> - update i_cluster_size
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: fix to avoid mmap vs set_compress_option case
https://git.kernel.org/jaegeuk/f2fs/c/3174a6dbb945
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
prev parent reply other threads:[~2023-07-17 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 2:06 [f2fs-dev] [PATCH v3] f2fs: fix to avoid mmap vs set_compress_option case Chao Yu
2023-07-17 17:34 ` 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=168961526181.4078.12987776501092675695.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 \
/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;
as well as URLs for NNTP newsgroup(s).