From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: allow empty mount string for Opt_usr|grp|projjquota
Date: Mon, 6 Apr 2026 16:59:04 +0000 [thread overview]
Message-ID: <adPmWCgtruKjGDYO@google.com> (raw)
In-Reply-To: <20260331174326.231867-1-jaegeuk@kernel.org>
Let's check mmap writes onto the large folio.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/file.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 2c4880f24b54..652b4534349b 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -82,7 +82,8 @@ static vm_fault_t f2fs_vm_page_mkwrite(struct vm_fault *vmf)
int err = 0;
vm_fault_t ret;
- if (unlikely(IS_IMMUTABLE(inode)))
+ if (unlikely(IS_IMMUTABLE(inode)) ||
+ mapping_large_folio_support(inode->i_mapping))
return VM_FAULT_SIGBUS;
if (is_inode_flag_set(inode, FI_COMPRESS_RELEASED)) {
--
2.53.0.1213.gd9a14994de-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2] f2fs: allow empty mount string for Opt_usr|grp|projjquota
Date: Mon, 6 Apr 2026 16:59:04 +0000 [thread overview]
Message-ID: <adPmWCgtruKjGDYO@google.com> (raw)
In-Reply-To: <20260331174326.231867-1-jaegeuk@kernel.org>
Let's check mmap writes onto the large folio.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/file.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 2c4880f24b54..652b4534349b 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -82,7 +82,8 @@ static vm_fault_t f2fs_vm_page_mkwrite(struct vm_fault *vmf)
int err = 0;
vm_fault_t ret;
- if (unlikely(IS_IMMUTABLE(inode)))
+ if (unlikely(IS_IMMUTABLE(inode)) ||
+ mapping_large_folio_support(inode->i_mapping))
return VM_FAULT_SIGBUS;
if (is_inode_flag_set(inode, FI_COMPRESS_RELEASED)) {
--
2.53.0.1213.gd9a14994de-goog
next prev parent reply other threads:[~2026-04-06 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 17:43 [f2fs-dev] [PATCH] f2fs: allow empty mount string for Opt_usr|grp|projjquota Jaegeuk Kim via Linux-f2fs-devel
2026-03-31 17:43 ` Jaegeuk Kim
2026-04-06 16:07 ` [f2fs-dev] " Daeho Jeong
2026-04-06 16:07 ` Daeho Jeong
2026-04-06 16:59 ` Jaegeuk Kim via Linux-f2fs-devel [this message]
2026-04-06 16:59 ` [PATCH v2] " Jaegeuk Kim
2026-04-06 17:34 ` [f2fs-dev] " Daeho Jeong
2026-04-06 17:34 ` Daeho Jeong
2026-04-13 9:40 ` [f2fs-dev] [PATCH] " Chao Yu via Linux-f2fs-devel
2026-04-13 9:40 ` Chao Yu
2026-04-13 23:00 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-13 23:00 ` 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=adPmWCgtruKjGDYO@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.