From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: chao@kernel.org, Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: disallow mmap write and data-modifying fallocate on atomic files
Date: Fri, 9 Oct 2026 16:35:44 +0800 [thread overview]
Message-ID: <63812000-4677-4af6-a3e1-4e87e39f0d88@kernel.org> (raw)
In-Reply-To: <20261002171704.3652570-1-daeho43@gmail.com>
On 10/3/26 01:17, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Stores through a shared writable mapping and fallocate with
> FALLOC_FL_PUNCH_HOLE, FALLOC_FL_ZERO_RANGE, FALLOC_FL_COLLAPSE_RANGE or
> FALLOC_FL_INSERT_RANGE do not go through ->write_begin, so they bypass
> the COW inode and modify the original inode directly. Reject them while
> the file is in atomic write mode, as fallocate already does for pinned
> and compressed files. A write fault gets SIGBUS and fallocate gets
> -EOPNOTSUPP.
>
> fallocate without these flags only preallocates blocks and stays
> allowed.
>
> Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> fs/f2fs/file.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index ef4d218e694..56c686b8580 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -140,6 +140,10 @@ static vm_fault_t f2fs_vm_page_mkwrite(struct vm_fault *vmf)
> return VM_FAULT_SIGBUS;
> }
>
> + /* mmap stores bypass the COW inode and would break atomicity */
> + if (f2fs_is_atomic_file(inode))
> + return VM_FAULT_SIGBUS;
Will we suffer race issue due to the check w/o lock?
Thanks,
> +
> if (is_inode_flag_set(inode, FI_COMPRESS_RELEASED)) {
> err = -EIO;
> goto out;
> @@ -2113,9 +2117,11 @@ static long f2fs_fallocate(struct file *file, int mode,
>
> /*
> * Pinned file should not support partial truncation since the block
> - * can be used by applications.
> + * can be used by applications. Atomic files should not either, since
> + * these modify the original inode directly and break atomicity.
> */
> - if ((f2fs_compressed_file(inode) || f2fs_is_pinned_file(inode)) &&
> + if ((f2fs_compressed_file(inode) || f2fs_is_pinned_file(inode) ||
> + f2fs_is_atomic_file(inode)) &&
> (mode & (FALLOC_FL_PUNCH_HOLE | FALLOC_FL_COLLAPSE_RANGE |
> FALLOC_FL_ZERO_RANGE | FALLOC_FL_INSERT_RANGE))) {
> ret = -EOPNOTSUPP;
next prev parent reply other threads:[~2026-10-09 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 17:17 Daeho Jeong
2026-10-09 8:35 ` Chao Yu [this message]
2026-10-09 15:05 ` [f2fs-dev] " Daeho Jeong
2026-10-10 1:40 ` Chao Yu
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=63812000-4677-4af6-a3e1-4e87e39f0d88@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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
all inboxes | Powered by JetHome®