From: Matthew Wilcox <willy@infradead.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Yuan-Hao Hsu <aa9736195201@gmail.com>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
David Hildenbrand <david@kernel.org>,
Linux MM <linux-mm@kvack.org>,
Christian Brauner <brauner@kernel.org>,
"zhangyi (F)" <yi.zhang@huawei.com>,
tujinjiang@huawe.com
Subject: Re: [PATCH] ovl: implement ->get_unmapped_area()
Date: Fri, 28 Aug 2026 13:41:50 +0100 [thread overview]
Message-ID: <apGCDtf-gE1osJqE@casper.infradead.org> (raw)
In-Reply-To: <CAOQ4uxjxDV0U9yrDA_StN968P_6cpjRAN2mBCx1c_RYd7BF4Og@mail.gmail.com>
On Fri, Aug 28, 2026 at 02:23:11PM +0200, Amir Goldstein wrote:
> Since mmap is going through backing_file_mmap() probably a good idea to
> pass this method through a backing_file helper as well.
>
> But more importantly, adding MM people to this patch review, mainly the ones
> that participated in the discussion over patch to fix similar issues
> in 2024 [1].
> Most of the concerns in that patch seem to have been addressed (?)
>
> [1] https://lore.kernel.org/linux-unionfs/20241205143038.3260233-1-tujinjiang@huawei.com/
No, not at all. All this patch needs to be is:
+++ b/fs/overlayfs/file.c
@@ -657,6 +657,7 @@ const struct file_operations ovl_file_operations = {
.fallocate = ovl_fallocate,
.fadvise = ovl_fadvise,
.flush = ovl_flush,
+ .get_unmapped_area = thp_get_unmapped_area,
.splice_read = ovl_splice_read,
.splice_write = ovl_splice_write,
All this "oh we have to call the underlying filesystem's
get_unmapepd_area" betrays a lack of understanding of the problem.
And Lorenzo suggested this in the linked thread:
https://lore.kernel.org/linux-unionfs/69b72e3d-b101-4641-9ce5-51346c93a98d@lucifer.local/
next prev parent reply other threads:[~2026-08-28 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 17:07 Yuan-Hao Hsu
2026-08-28 12:23 ` Amir Goldstein
2026-08-28 12:41 ` Matthew Wilcox [this message]
2026-08-31 8:18 ` Miklos Szeredi
2026-09-14 11:42 ` Yuan-Hao Hsu
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=apGCDtf-gE1osJqE@casper.infradead.org \
--to=willy@infradead.org \
--cc=aa9736195201@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=miklos@szeredi.hu \
--cc=tujinjiang@huawe.com \
--cc=vbabka@suse.cz \
--cc=yi.zhang@huawei.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®