linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: 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:39:35 +0200	[thread overview]
Message-ID: <eb153cdb-6228-435a-916a-77f4166d4cd2@redhat.com> (raw)
In-Reply-To: <20240405180038.2618624-1-willy@infradead.org>

On 05.04.24 20:00, Matthew Wilcox (Oracle) wrote:
> Remove four hidden calls to compound_head().  Also exit early if the
> filesystem block size is >= PAGE_SIZE instead of just equal to PAGE_SIZE.
> 
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Reviewed-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
>   mm/truncate.c | 36 +++++++++++++++++-------------------
>   1 file changed, 17 insertions(+), 19 deletions(-)
> 
> diff --git a/mm/truncate.c b/mm/truncate.c
> index 725b150e47ac..e99085bf3d34 100644
> --- a/mm/truncate.c
> +++ b/mm/truncate.c
> @@ -764,15 +764,15 @@ EXPORT_SYMBOL(truncate_setsize);
>    * @from:	original inode size
>    * @to:		new inode size
>    *
> - * 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 nearest write access to
> - * the page.  This way filesystem can be sure that page_mkwrite() is called on
> - * the page before user writes to the page via mmap after the i_size has been
> - * changed.
> + * 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/ ?

>    *
>    * The function must be called after i_size is updated so that page fault
> - * coming after we unlock the page will already see the new i_size.
> + * coming after we unlock the folio will already see the new i_size.
>    * The function must be called while we still hold i_rwsem - this not only
>    * makes sure i_size is stable but also that userspace cannot observe new
>    * i_size value before we are prepared to store mmap writes at new inode size.
> @@ -781,31 +781,29 @@ void pagecache_isize_extended(struct inode *inode, loff_t from, loff_t to)


Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb


  reply	other threads:[~2024-04-09 13:39 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 [this message]
2024-04-09 14:09   ` Matthew Wilcox
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=eb153cdb-6228-435a-916a-77f4166d4cd2@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=p.raghav@samsung.com \
    --cc=willy@infradead.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).