From: Matthew Wilcox <willy@infradead.org>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH] mm: Convert pagecache_isize_extended to use a folio
Date: Tue, 9 Apr 2024 15:09:40 +0100 [thread overview]
Message-ID: <ZhVMJF6fICFVO6Lc@casper.infradead.org> (raw)
In-Reply-To: <eb153cdb-6228-435a-916a-77f4166d4cd2@redhat.com>
On Tue, Apr 09, 2024 at 03:39:35PM +0200, David Hildenbrand wrote:
> On 05.04.24 20:00, Matthew Wilcox (Oracle) wrote:
> > + * Handle extension of inode size either caused by extending truncate or
> > + * by write starting after current i_size. We mark the page straddling
> > + * current i_size RO so that page_mkwrite() is called on the first
> > + * write access to the page. The filesystem will update its per-block
> > + * information before user writes to the page via mmap after the i_size
> > + * has been changed.
>
> Did you intend not to s/page/folio/ ?
I did! I think here we're talking about page faults, and we can control
the RO property on a per-PTE (ie per-page) basis. Do you think it'd be
clearer if we talked about folios here? We're in a bit of an interesting
spot because filesystems generally don't have folios which overhang the
end of the file by more than a page. It can happen if truncate fails
to split a folio.
> Reviewed-by: David Hildenbrand <david@redhat.com>
Thanks!
next prev parent reply other threads:[~2024-04-09 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 18:00 [PATCH] mm: Convert pagecache_isize_extended to use a folio Matthew Wilcox (Oracle)
2024-04-09 13:39 ` David Hildenbrand
2024-04-09 14:09 ` Matthew Wilcox [this message]
2024-04-09 14:27 ` David Hildenbrand
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=ZhVMJF6fICFVO6Lc@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=p.raghav@samsung.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;
as well as URLs for NNTP newsgroup(s).